I have some earth-shattering news to share… Software Engineering is hard. Expectations for Software Engineers (as opposed to programmers) are high. We’re expected to have an ever-broadening spectrum of knowledge, and to be able to…
Orange Slice Where you get your monthly slice of BTI360 BTI360 HQ’s @ 3:30 p.m. Agenda 3:30 – Code Kata: What Do Boy Scouts Know About Clean Coding? Every Boy Scout knows that you leave the camp…
We’ve talked about how Clean Code leads to better naming and focused functions. Both have a huge impact on how quickly the development team can respond to change. But there’s another piece, without which, the…
Continuing our Clean Code discussion, imagine you have a textbook from which you only need information from a single section. Now imagine that textbook has neither chapters, nor sections or paragraphs, and is even lacking…
As we continue our discussion of Clean Code, I’d like to begin by asking you a question…What book do you think best serves as a daily reference for improving the readability and understandability of our…
Clean Code is important for developers and managers. Last week in our post about the difference between programmers and engineers, we made the argument that software engineers – not programmers – are what we need…
Programmers: stop calling yourselves engineers. That was the title of an article I found myself reading a couple months ago. Of its many points about the difference between programmers and software engineers, I summarize them…
Close Form
Then stay up-to-date with our latest posts delivered right to your inbox.
Whether we’re honing our craft, hanging out with our team, or volunteering in the community, we invite you to keep tabs on us.