I've been recently doing a lot of test-driven development at my new job, and one of the things I've noticed is that sometimes we will just run into snags, times when we hit a wall where it feels like we aren't making any real progress forward. There have been a few times now where we have gotten the code down to make the actual product work, but we spend a lot of time struggling to get the tests to pass and to really test the system in a way they we felt was good and proper. The trick is juggling the fact that we want to be a lean team that develops quickly but that we also want to write tests first that will pass when we implement these new features. Sometimes that last "making the test pass when they should" can be a lot more challenging that it ought to be, and it sometimes seems that we're put in a position where we need to choose between cutting corners or further increasing the risk that we ship late. To be honest I don't really have a right answer for all this, but in this post I'll think out loud about some ideas.
I’ve been working as a software consultant for the past few weeks, and an interesting thing happened. The initial aggressive plan was to build a working prototype in 2 weeks that involved a React web front-end, Postgres db, and node backend api. Well, we wanted to not do a complete faceplant so we were kind of forced into cutting corners and optimizing for speed. For that reason and also since one of our three engineers was somewhat of a Ruby expert we thought it was be a quick win to quickly build out the backend api in ruby on rails. This post is me reflecting on my experiences today pair programming in Ruby on Rails.
This is a short little post about choosing font colors when building software applications. In web development, if you don't specify a font color (ie the css property "color") then it will default to black, and black straight up #000000 black is really not a very good choice for a font color...
As a professional software developer I have had the luxury of being able to work on successful professional projects in AngularJS, React, and now the modern Angular. To me it's so funny how similar the two frameworks are in terms of the problem they are trying to solve and even the way they do it.
The posts on this site are written and maintained by Jim Lynch. About Jim...