The tech industry needs to be more inclusive of women and people of color. It's about having the largest pool to draw excellence from. Sadly, most of the discussion, even the discussion that is advocating for a more inclusive culture, itself is divisive.
Because we know what it is like to read and debug a 500-line method. And we don’t want to go through it again. Because we’re sure the other guys’ code can use improvement. Even if they thought otherwise.
Amazon Web Services offer various tools for building distributed and scalable workflow applications. One approach for building such an application is to use topics and queues for connecting the distinct steps in the workflow process.
While some providers tout the evils of running agents on your system and can oft be heard shouting, “no agents here!!!”, we prefer to keep an open mind. That being said, like most things in life, agents have their pros and cons.
In an agile team, especially with continuous integration, we don’t notice handoffs. Continuous integration makes handoffs trivial. If we work together to achieve a feature, as in swarming or mob-programming, we don’t even have handoffs.
A few days ago I made the case that the most efficient code review process is one that deals with reviews within minutes of hours of the commit they pertain to. I didn’t dwell so much on the difference between pre-commit reviews (that until they “pass”, the commit can’t go in), and post-commit reviews (which suggest prioritized follow up work in the case of “fail”).
We need to be aware of any peculiarities of the real development process to select a tool that would be capable to replicate it. So, what are the things to note about the process that one would definitely need in the tool?
GitHub publishes a command line tool called hub, which is a more convenient way than the website for doing a few specific tasks and in particular I've been using it more and more for opening pull requests. The basic workflow is to create a branch, add your changes, and then push it to GitHub
If we knew exactly what code needs to be written, what needs to be done and how it can be done, we would need very little time to write it. It is the discovery of the knowledge what to build and how to build it that takes all the time.
I do not see Windows Azure SQL Database as a feasible solution for a firm that expects its business to scale. The only way to migrate from Windows Azure SQL Database is to export its data and import it on a regular instance, and it's not acceptable when you have a significant traffic.
After J.B. Rainsberger reviewed my astronaut solution during his course, I found out there were still some points to address and duplication to be removed; so I set out on performing the kata again with reuse in mind. As always, spoilers ahead.
"Yesterday, I was in Sprint Planning…” I hear it once, and I’m suspicious. By the time the third team member says this, it’s clear the Daily Scrum I’m observing is broken. Everyone in the room knows we did planning yesterday—we were all there
Aaron speaks with Chip Childers (@chipchilders) for a quick update on Apache CloudStack as well as what's next in IaaS and how to provide services (DBaaS, Message Bus, LBaaS, etc.) above IaaS and what the future may hold.