I’ve been using the CefSharp.Offscreen library to drive the Chromium browser for a couple of months now. While the code I’ve been working on has been working correctly, I could never figure out why so many instances of Chromium are left dangling in my task manager. Oh, they’d all go away once I exited the application, but then it would take a very long time for my application to completely close because there were so many instances of Chromium hanging around.
This past week, I finally figured out how to keep the number of Chromium instances in line with the number of off-screen browser windows I was actually creating.
I’ve been looking at Angular.js recently. I’ve already got enough of a project done in MongoDB (with Mongoose), Express, Angular and Node.js (MEAN) to be comfortable with how Angular works. But I wanted to give it a try using ASP.NET as the back end. I’m always learning. Always improving.
To start out, I just setup an index.html page to hold my basic form as I got the basic look and feel going. But as I progressed, I wanted to make sure I progressed, I wanted to add in the capability of using Angular’s html5mode for the client side routing.
Out of the box, Angular, and most other frameworks that implement client side routing, using the hash symbol to specify the route. For example
This allows the routing to work on older browsers.
ASP.NET, Angular.js & html5mode
Recently someone asked me where the business rules should go in an MVC framework. The Model or the Controller?
This reminded me of a post I wrote when ASP.NET MVC was first released.
But today I want to cover a broader topic common to everyone, not just programmers. Not being able to think outside the box.
I’ve noticed a trend recently. Someone will write a post about some technical interview question and someone will write a comment about how that’s such a dumb question that they wouldn’t even bother answering it. I’ve actually been that guy recently. John Sonmez wrote about “Cracking the Coding Interview” and I responded that I don’t do coding interviews. In fact, I wrote a whole post about this. But as John pointed out, this may actually cause you to be limiting your career. You wouldn’t answer that question for a 33% raise? Really? There isn’t anything that could motivate you to consider answering a question that you feel is useless, stupid or dumb?
This week, I saw another post about some technical interview question that someone said he wouldn’t answer. Sorry, I don’t have a link for that one, I wish I did.
And then add to this, the number of useless interview questions I have answered in the last year. Why did I answer them? Because I could. Because the challenge was actually fun.
And so, let’s reconsider the arrogant stance of “Thanks for your time, I’ll show myself out.”
First let’s consider why we might not want to answer a particular question.