Enable your blog comments already!
Sorry for the mini-rant here…
Sorry for the mini-rant here…
Normally I have multiple vm’s running for various different projects - all of these are in VMWare Workstation instances I toggle between suspend and started. I decided to create a script and an Ubuntu launcher icon for toggling the vms back and forth.
As you may or may not be able to tell, I use Wordpress on this website. So, I guess that makes me a fan… (trust me, as a programmer, I’ve always toyed around with writing my own custom blog software just for my domain - but alas, other aspirations always trumped that. Plus, wordpress is perfect for what I need.)
Estimates can be one of the hardest things to create as a developer. The word estimate is a misnomer in our industry. It’s almost as if they should be called “agreements” or “promises” according to some bosses. Yet we all know that they are just that: an estimate of the amount of time, not a guarantee.
MooTools, a common Javascript framework, is responsible for extending an array in Javascript. It adds a number of useful features to each array that is created.
In part 1, I discussed the various arguments I run into about wanting to be overly security conscious with our sites in regard to third party javascript. In this entry, we’ll run through a few scenarios.
I have the argument a lot with product managers about allowing custom HTML and Javascript into our projects. I don’t want to do it. I want to only put in predefined, sanitized information. But more about my reasons after this… let’s look at the arguments I get first…
2019-11-11 Update This extension has been removed from the Google Chrome Extensions store and the repo has been archived.
I use Chrome almost exclusively now. One thing that drove me nuts was the lack of support for FirePHP in the console of Chrome. Google even released some extensions for it - but they either didn’t work or were out of date. So I created my own.
After transitioning away from the doomed Google Reader to Feedly, I found it to be awesome! I only had one gripe with the shortcut key scenario… when you went to view the entire article in a new tab, it was always focused. This meant I’d still have to middle click with my mouse to put my tabs in the background.
When doing a bit of code review, I saw an incredibly ornately architected future-proof module written by one of my programmers on my team. It had taken him roughly 3x as long as I had estimated, but the code was very complete. It was created in such a way that every single portion of it was modular and could be interchanged quite easily.