The Stride Blog
Get the latest tips on agile software development so you can scale and embrace change.
The mobile application revolution took off in 2008, when Apple allowed third-party applications for the iPhone. While it's way too early to say that ship has sailed, many companies and developers are looking for the next big thing.
It’s Thursday morning at 10:30am. Kim, Head of Product at Acme Co., confronts Kevin, CTO of Acme Co:
At Stride, we call our employees “developer consultants.” It’s a term that not many folks use, so let’s talk about what a developer consultant means to us at Stride.
As an entrepreneur, it’s easy to get caught up in the excitement around your idea. You pour blood, sweat and tears into your idea, speak to tons of potential customers and feel you’re really on to something big. Now, all you’ve got to do is build and launch the thing. Easy right? Not so fast. Selecting the right tech stack for your project is a key decision that you need to make. But, with a bit of forethought, choosing the right stack is doable, even if you’ve never written a line of code in your life, and it pays dividends for years to come.
Your enterprise shouldn't just think like a startup. Act like one. Get our MVP launch guide to fix your MVP launch today.
I am a huge fan of the New York Times, but today’s article, “Uber Case Could Be A Watershed for Women in Tech,” really pissed me off. Yes, it is absolutely true that many forms of harassment against women in the workplace have been going on forever, and yes it is true that sometimes, the individuals responsible for said harassment go unpunished. And it is also true that there are many bro-grammer cultures that can’t seem to figure out how to treat all employees fair and equally. But, the New York Times article quotes Freada Kapor Klein, a partner at the venture capital firm Kapor Capital and an Uber investor. Ms. Kapor Klein states that an Uber employee asked her, in regards to harassment of women in the workplace, ‘Has anyone gotten it right in tech?’” and her response was “not yet. And that means an opportunity for Uber.”
Not only is a fixed bid project a bad idea, it’s actually a myth and doesn’t in fact exist. Let me explain. Let’s say you want to launch an MVP, build a new product, or upgrade an existing application. You have a vision and scope. You also have a budget in mind. And now, you set out to build and launch the product. You find a team to build your product and then you ask, “How much is this going to cost?”
At Stride, we put a lot of thought into our internal mentorship program, and a big part of that is distinguishing the role of the mentor from the role of the manager. This distinction is useful for anyone who wants to be a mentor, so we’d like to share our thoughts on the matter. Perhaps it will be helpful to you.
Pair programming is probably the most controversial and least-adopted Agile practice. Capers Jones finds that for defect removal it’s relatively expensive compared to other techniques, though he doesn't take other advantages of pair programming into account. (In his comparison of methodologies, XP as a whole comes out at or near the top in terms of schedule and total cost of ownership.) There is no denying that pairing is a highly visible cost to management: "Two developers at one workstation? No way! We already pay them a fortune!"