3 ms·
When you develop in a rush, SCRUM style, perhaps in the stereotypical silicon valley mode, you can only spit out code, your goal is just to be quick and achieve
by kkfx 4y ago
When you develop in a rush, SCRUM style, perhaps in the stereotypical silicon valley mode, you can only spit out code, your goal is just to be quick and achieve some apparent level of usability.
If you can calmly think about something to automate, made good scenario, do some mental experiments etc than you can craft good code, witch happen to be also secure in general. But such model is long lost.
- lp4vn 4y agoExactly, OP probably lives in a bubble. A lot of projects are just about showing the stakeholders the maximum possible and the rest is irrelevant. There is not enough time even for refactoring or paying a bit of the technical debt, let alone making the application safe.
- akkartik 4y agoThe way I think about it is: I can either program calmly for myself or in SV mode for millions of "users". And when I look around, my dilemma seems fairly common. Programming for lots of people is inhuman. I don't yet know how to program calmly and get to something others find useful. It takes too long, nobody will fund it, I can't convince others to join me, even I can only devote limited time to it. So my conclusion is: calm programs only happen when people are willing to be more than users, to take ownership of them and agency in their evolution. And that's the kind of people I build for: http://akkartik.name/about http://akkartik.name/about http://akkartik.name/post/roundup22 http://akkartik.name/post/roundup22 https://github.com/akkartik/mu https://github.com/akkartik/mu