4,421 karma · joined June 6, 2012
Over time, I've found that the only reliable way to reason about engineering decisions is to work backward from the business use case. What are we trying to accomplish? What's the time frame? What risks are worth taking now vs later? Everything else...patterns, paradigms, "best practices"...only make sense in that context. The rest is academic, and often divorced from reality tbh.
Also noticed that many strong opinions in engineering come from people trying to avoid pain they've experienced before. But the solution that saved them in one situation can easily become a liability in another. Patterns ossify into rules. That's why I try to keep my reasoning grounded in outcomes and context, not ideology. Most "best practices" are just local maxima..useful until they arent.
> No need to revise algorithms and data structures before interviewing with us.
It seems this should read: "No need to review algorithms and data structures before interviewing with us."
> fDeploy is a self-hosted deployment software for Windows being currently built in Stockholm, Sweden by developers with over 10 years of experience in the industry, focusing only on the most essential and most valuable features.
I'd recommend focusing on what the most valuable features are and making those the highlight. Leading with who is building it and where doesn't add much unless your team is especially well-known or noteworthy. Also, citing "10 years of experience" as social proof might not resonate strongly—it's not a differentiator for most audiences (10 years is not that long). Instead, consider showcasing the unique aspects of the product that would immediately grab attention.
(I'm not agreeing or disagreeing with any of this, just saying this is the internally consistent approach.)
Newton, Steve Jobs, Marie Curie...the list goes on. These people's success wasn't a product of balance or moderation
To some extent, the concept must remain vague because its meaning will vary from one company to another. Typically, there are one or two critical aspects that are most important for a startup or company, and the founder must be involved in those areas in a way that conflicts with the usual corporate structure or hierarchy.
Anyways, this is how I understood it.