3 ms·
People need to focus more on getting results. We're collectively so steeped in posturing about technology stacks and idiosyncratic decisionmaking that we've mis
by tmpanon1234act 10y ago
People need to focus more on getting results. We're collectively so steeped in posturing about technology stacks and idiosyncratic decisionmaking that we've missed the bigger picture: get something done. For instance, anyone who says they factored in all the tradeoffs and then chose Haskell isn't trying to get things done or build a sustainable business - they're trying to orchestrate a technological boondoggle.
At the end of the day no one cares if you're a good developer. They care that the service looks good and works well. Googling is how you build a better service ergo do it and don't worry about it.
- smileysteve 10y ago> We're collectively so steeped in posturing about technology stacks and idiosyncratic decisionmaking that we've missed the bigger picture: get something done. > At the end of the day no one cares if you're a good developer. They care that the service looks good and works well. Those decisions lead over time to an architecture that can good or bad, and assuming your software has patches or improvements over time, that's important. Context: I've worked with too many startups with non-dry untested code that are now getting past "looks good and works well" to needs to drastically expand feature set or change underlying features.
- tmpanon1234act 10y agoWe do heavy backend unit/integration testing, less so on the frontend and a lot of UAT. It's good enough to move fast with some confidence but yes sometimes you have to do tough things and that comes from experience. I recently wrote a distributed, cache-coherent session store for instance. Googling is necessary not sufficient.