45 ms·

But adding functionality grows in effort as more code is added. At some point it makes sense to improve a code base so you improve the rate at which you are get

by mden 10y ago

But adding functionality grows in effort as more code is added. At some point it makes sense to improve a code base so you improve the rate at which you are getting "there". In fact there are a lot of code bases, perhaps most, which simply cannot get there in any sane way and fall short of achieving their goal. You might not care how goals are achieved as a user but as an engineer it's worth exploring and discussing different approaches.

deleted 10y ago
[deleted]
thesmallestcat 10y ago
I had no idea!
ArkyBeagle 10y ago
I care more as a user than as an engineer. :) Just to be clear - I don't suspect that the things that pretend to replace C are bad, or no good. I've just seen multiple "pretenders to the throne"[1] and what would appear to have happened is that we just moved the pathology around. [1] please excuse the horrible metaphor. After a few iterations of that, one begins to think that perhaps this is a distinctly human problem that is not necessarily addressable by improved language systems. My greatest concern is that I keep seeing people learn the same things, over and over, on the job. There's no real repository of literature to actually address any of this - each engineer appears to have to learn it mostly from scratch. There's a famous bon mot from pubic choice economics - "something must be done; this is something; this must be done." I just hope all the new crop of languages are not that. Finally: If you can, and if you can learn the right patterns ( isn't that true of all languages, though?), the thing I have gone to, again and again that is better than test equipment in terms of reliability continues to be Tcl.
- pjmlp 10y ago
  > There's no real repository of literature to actually address any of this - each engineer appears to have to learn it mostly from scratch. It is called university and engineering degree in software development.
  - ArkyBeagle 10y ago
    Each and every person I have observed learning this over and over has a university degree. "CS ain't coding", as they say.

by mden 10y ago

deleted 10y ago

[deleted]

thesmallestcat 10y ago

I had no idea!

ArkyBeagle 10y ago

I care more as a user than as an engineer. :) Just to be clear - I don't suspect that the things that pretend to replace C are bad, or no good. I've just seen multiple "pretenders to the throne"[1] and what would appear to have happened is that we just moved the pathology around. [1] please excuse the horrible metaphor. After a few iterations of that, one begins to think that perhaps this is a distinctly human problem that is not necessarily addressable by improved language systems. My greatest concern is that I keep seeing people learn the same things, over and over, on the job. There's no real repository of literature to actually address any of this - each engineer appears to have to learn it mostly from scratch. There's a famous bon mot from pubic choice economics - "something must be done; this is something; this must be done." I just hope all the new crop of languages are not that. Finally: If you can, and if you can learn the right patterns ( isn't that true of all languages, though?), the thing I have gone to, again and again that is better than test equipment in terms of reliability continues to be Tcl.

pjmlp 10y ago
> There's no real repository of literature to actually address any of this - each engineer appears to have to learn it mostly from scratch. It is called university and engineering degree in software development.
- ArkyBeagle 10y ago
  Each and every person I have observed learning this over and over has a university degree. "CS ain't coding", as they say.