The sloppy, wild, cocaine-fueled, copy-paste hacking will continue until morale improves.
Discussion
Thank god.
Yeah, but it's pure research and hacking for the fun of it; no development.
That's really fun, I know, but we need more engineers, to get production-quality systems. People who understand how to set a goal, break the goal down into stages, and then focus and work toward that goal over a medium stretch of time, like 6 months to 2 years, followed by years of further development and maintenance _on the same system_. And, ideally, that person should be capable of working together with other people, so that you can have more than one person maintaining one system.
Engineers are developers with a low time-preference, basically. They think things through, before beginning, they work cleanly and carefully, they are reliable, and they are empathetic with the end users. That's why they're craftsmen, instead of hackers. They build things that people are meant to actually use.
It's the difference between a fancy chair, some artist conceived of, that looks great standing in a museum, and a chair that a master carpenter built, who spends all day producing various chairs. Which one would you prefer to sit on, every day, for years? Who would you take the chair to, if the chair broke? The artist? The artist can't even remember building that chair, and he's moved on to making pottery.
>>
The research portion occurs when a company's R&D team tests the viability of a potential product. This is the act of discovering new sciences that can be used to create new products. The development portion comes after the research and is the act of turning the discovered science into a useful product that the company can market and sell.
<<
2 things.
Plato's ideal forms.
A "Systems Engineer".
Second one is more important in the short to medium term.
Changing FIAT ways!
There are two wolves inside you.
I'm trying to shake off my inner hacker and get back to engineering, so that I actually produce something useable, that adds value to the market.
Hacking is a good way to get to know the lay of the land, before you lay down the actual roads.
Hack towards a solution once, throw it all away. Hack a better solution, throw it all away again. Only then build it properly with the gathered knowledge and experience of the problem.
Yeah, that's how I work.