Software Engineering

Making Informed Decisions on Trade-offs

Every time you sit down to create a piece of software, you are making choices about what matters and what doesn’t. Often we place our own comfort and productivity over that of the users of our software. That’s often a wise thing to do in environments like a startup, where the cost of delay is high. Maybe a day of developer time is expensive, and cutting corners is worth the money. Sometimes, though, the responsiveness of the user experience is your central value proposition. When that’s the case, traditional corporate best practices don’t cut it, and you need experienced developers that can shift the focus to fundamentals.

In a high throughput environment or busy site, the economics changes. Many popular frameworks and practices will consistently add large chunks of time to each request or transaction. That might sound OK to begin with, but when you grow to handle thousands of those requests every second, the cummulative cost adds up to months of downtime over the lifetime of your product. That equates to money, good will and opportunities lost in the long run. A good software engineer will help you make informed decisions about where to focus your efforts and where to save money.

If you think this doesn’t apply to you or your company, think again! The business of software development is changing. The technology literacy of the public is growing, and with it their expectations. If you have competitors that provide a smarter, better or more reliable experience they will steal your business. Can you afford not to care about the fundamentals? Read more on how to adapt to the future here.


Create a website or blog at

Up ↑

%d bloggers like this: