Re:Using a Framework will harm the maintenance of your software
by ativzzz on Wednesday October 12, 2022 @09:26PM
(#33186068)
I shudder to think about what a formal specification of some of the full stack web projects I've developed would look like. They might take longer than the actual coding of it - especially because specifications change mid project as we build things and realize we actually want them different.
Note this is a feature, not a bug, of "agile" development - you learn and adjust on the fly
Re:Using a Framework will harm the maintenance of your software
by ChrisMarshallNY on Wednesday October 12, 2022 @09:42PM
(#33186174)
I tend to make it up as I go along ([0], [1]). It works for me (I just finished up a new SDK, using this technique[2]).
However, this would not work for many outfits. It’s just the way that I work.
WFM. YMMV.
[0] https://littlegreenviper.com/miscellany/forensic-design-docu...
[1] https://littlegreenviper.com/miscellany/evolutionary-design-...
Re:Using a Framework will harm the maintenance of your software
by ChrisMarshallNY on Thursday October 13, 2022 @05:16AM
(#33188882)
Hmm… That’s interesting.
I seem to have upset people. I’d certainly be interested in knowing why, as my comment directly addresses the parent, and does not coarsen the discourse.
Yes, it appears that companies won't budget that at all. Many seem to ship fast, fix later. It is also on the customer, really.
Some people expecting software developers to deliver high quality software (with near 100 % code coverage and exceptional performance), but paying them less and less, is not fair. No wonder, some devs are incentivized to skip unit tests or error handling. Because some employer or some customer won't pay for it.
This is the status quo that makes me pessimistic. It appears that software development is gluing things together and make it somehow work.
This ain't fun for me.