4 ms·
“Best practices” smells like such a marketing term it should be tossed in the bin. It’s poetic language that has nothing to do with specific problems. What pe
by chmsky00 5y ago
“Best practices” smells like such a marketing term it should be tossed in the bin.
It’s poetic language that has nothing to do with specific problems.
What people usually mean when it comes to engineering is “be safe, reliable, and correct.”
Security best practices to be safe.
Developer best practices for reliability.
Etc etc
“Best practices” is hand wave-y fluff for “do a good job” and doesn’t need a technical definition.
Make sure you’re secure, reliable, and correct given the engineering context, and odds are you result in a system that also has a lot of specific best practices in place.
- Dudeman112 5y agoI think it's very telling just how little engineering there is in Software Engineering that people can call best practices "just preferences" or "marketing fluff" and not be immediately laughed out of the room. Because that's what would happen if someone suggested "best practices smells like a marketing term" in an actual engineering discipline.
- soco 5y agoWhich brings to the realization that we have a lot of software development and much less software engineering.
- chmsky00 5y agoEngineer to solve the problem. Not banter online. My problem is people take a slogan like best practices and copy-paste in every new framework because it’s de facto best practice. If the business is one of 1,000 todo apps, sure copy paste. But it’s new hardware best practices are different and we ought to acknowledge that software use case isn’t as uniform as electronics, where Ohms law and material waste are coupled to waste. Language choice and syntax choice depends on the problem as the team sees it. Avoid buffer overruns, sanitize inputs. There you have it; software best practices.