Our Chief Architect Eric Melski just blogged about the consequences and limitations with correctness and performance when you’re dealing with recursive makes, backed up by some interesting metrics and insights. Eric’s also detailing how the design of Electric Make in ElectricAccelerator eliminates the biggest problems attributed to recursive make, without requiring a painful and costly [Read More →]
We recently talked to one of our customers implementing ElectricCommander, our software development and delivery automation solution, and the improvements this customer has seen with ElectricCommander are truly astounding. The customer (for privacy reasons, we shall not name them here), creates cutting edge software used by millions of web users/consumers around the globe. Their software [Read More →]
In a previous blogpost by Eric Melski, he covered the basic conflict detection algorithm in ElectricMake. It’s surprisingly simple, which is one of its strengths. But if ElectricMake strictly adhered to the simple definition of a conflict, many builds would be needlessly serialized, sapping performance. Over the years we’ve made a variety of tweaks to the [Read More →]
Parallel execution is a popular technique for reducing software build length, and for good reason. These days, multi-core computers have become standard — even my laptop has four cores — so there’s horsepower to spare. And it’s “falling over easy” to implement: just slap a “-j” onto your make command-line, sit back and enjoy the [Read More →]
This is part five of a five part series where we will present five distinct challenges that if left unaddressed will drastically reduce an organization’s ability to gain the benefits promised by a move to Agile development methods. It’s a sad fact that in most enterprises, the process of building, testing, and deploying software is [Read More →]
Hugely important, mutual respect makes it possible to work together efficiently. Respect yourself, your coworkers, and your customers. Expect the same from everyone on your team, and help those who run into any difficulties with that. Any feedback is of course welcome (I sure hope my team won’t correct me too much). Read the other [Read More →]
Of course, I know and use all the favorite feedback phrases (“My door is always open”, “Let’s have regular one on ones”, etc.) These are all good, but everybody is busy, so sometimes these happen, and sometimes they don’t. I am sure we have all had those pretty useless “Q: So how are things going?, [Read More →]
Team members are empowered to make their own decisions where appropriate and know when to consult. I personally don’t care for micro management (too much work for me), so when choosing members for my team I look for people with a strong sense of personal accountability who drive towards finding the best possible solution. That [Read More →]
In many organizations, there’s too much talk about setting goals and not enough doing it. Everybody needs to clearly understand the overall goal, and what they can do to help move forward with that goal. And let’s be clear… the overarching goal is to allow for my early retirement at a gorgeous beach on some [Read More →]
So, while I was counting and assigning bugs in Jira, I started to wonder… What makes our development team (well… probably any team) successful? Aside from me being an awesome manager dude (with tie-dye t-shirts and all), the obvious answer is: people. Now that we’ve taken care of that platitude, the real question is: How [Read More →]
