3 ms·
so to be clear, having such an artifact is better than having classical legacy code, because it shares all the same downsides but has a unique upside, being “we
by dustingetz 3y ago
so to be clear, having such an artifact is better than having classical legacy code, because it shares all the same downsides but has a unique upside, being “well tested, well documented, and elegant”
- Etheryte 3y agoAs someone who has worked with an artifact or a few over the years, I definitely agree. The most colorful example was when I tried to rewrite one from scratch just to thoroughly understand all the business logic in it. By the time I ironed out all the bugs my code was practically identical to the original.
- ehnto 3y agoPesky business logic does tend to get in the way of a nice concise program. Complex enough businesses are perhaps an Alien Artifact of their own.
- raverbashing 3y agoAh true the biggest obstacle to 'nice code' is all the quirks reality forces us to recognize We think "ah we just need this" but then there are multiple corner cases and your nice code turns into a mess