Sometimes the day of a developer gets awfully complicated. One of my less favorite moments are those when you have used a library for most of your project and then you realize you need things from it it was not designed to do.
There's a key on my keyboard that I have spent most of my typing career learning not to press. Right next to A and right above Shift, it seems impossible to avoid. It MAKES ME SOUND ANGRY when I'm not.
Processor Expert components are making things very easy to configure: go a component, use the component inspector and change a setting. However, with the devices getting more and more complex, the list of settings or properties get longer and longer. To the point that it is hard to find a setting.
Every once in a while, you have to put in a heroic effort to diagnose a bug. When you finally figure it out, you want to run around the office singing “We are the champions”, even if it turns out to be a trivial issue. Because that doesn’t mean it took a trivial amount of effort.
If nothing else, SDN in whatever definition you like, is giving us the concept of a programmable network. And what use is programming a network if all you use it for is to automate basic configuration information?
Back when Adam Cameron and I launched the ColdFusion UI - The Right Way project, I mentioned that initially we would accept submissions from the community to build out the content before releasing an actual readable version. Earlier this week I got off my rear and actually built a process to make this happen.
Basically EVERYONE is talking about it right now. But, really, why has it become so popular all of a sudden? Sounds like yet another web technology like any other else, right? Well, in a nutshell... (continue reading)
New developers joining a project will often find that the project won't build cleanly on their machine, and hours of time will be sunk into setting up the project so work can start. Counter this by using continuous integration to build your project from scratch.