| Deutsch English Français Italiano |
|
<vi4l5c$3fned$3@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder2.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Chris Ahlstrom <OFeem1987@teleworm.us> Newsgroups: comp.os.linux.misc Subject: Re: Joy of this, Joy of that Date: Tue, 26 Nov 2024 09:15:08 -0500 Organization: None Lines: 42 Message-ID: <vi4l5c$3fned$3@dont-email.me> References: <vhigot$1uakf$1@dont-email.me> <vhsdhp$1m6qu$2@dont-email.me> <X4KcnQQzFNko49_6nZ2dnZfqnPWdnZ2d@earthlink.com> <vhvdmo$2900d$3@dont-email.me> <vhvdqu$28p7r$7@dont-email.me> <vhvm34$2aerk$2@dont-email.me> <1b166410-ecc1-f9e5-7218-cde9618f4686@example.net> <lqi4odFdu06U3@mid.individual.net> <77840736-c143-e896-5da0-d0afae4915ed@example.net> <vi1p3r$2oh05$7@dont-email.me> <2118139f-4451-560b-5094-a3d61c05f0d3@example.net> <lqkh38Fpp09U2@mid.individual.net> <vi47lr$3cj2g$1@dont-email.me> <vi4hok$3f6em$1@dont-email.me> Reply-To: OFeem1987@teleworm.us Injection-Date: Tue, 26 Nov 2024 15:15:08 +0100 (CET) Injection-Info: dont-email.me; posting-host="7943a899bd1c40d7fa7d071c1777e471"; logging-data="3661261"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1885PBXj4OW899wSVyaC/yv" User-Agent: slrn/1.0.3 (Linux) Cancel-Lock: sha1:RjVgKuwOtqFDp4xI3exQH4KRHuk= X-Mutt: The most widely-used MUA X-Slrn: Why use anything else? X-Face: 63n<76,LYJQ2m#'5YL#.T95xqyPiG`ffIP70tN+j"(&@6(4l\7uL)2+/-r0)/9SjZ`qw= Njn mr93Xrerx}aQG-Ap5IHn"xe;`5:pp"$RH>Kx_ngWw%c\+6qSg!q"41n2[.N/;Pu6q8?+Poz~e A9? $6_R7cm.l!s8]yfv7x+-FYQ|/k X-User-Agent: Microsoft Outl00k, Usenet K00k Editions Bytes: 3274 Rich wrote this post while blinking in Morse code: > Pancho <Pancho.Jones@proton.me> wrote: >> >> <snip> >> >> The fundamental characteristic of a good programmer is to be able to >> deliver an application that is useful. Everything else is secondary. Nah, the application must also be maintainable. >> IT department standards for good "production code" were often dogmatic >> nonsense, labour intensive, often failures. Perhaps it has improved, but > > It has not. For "enterprise" style software at least. Our group had good practices, including design review, code-review, and plenty of documentation. >> in my day corporate IT management was dominated by snake-oil salesman > > Still present (ClownStrike anyone?). > >> using a team of very poor drone programmers. Management liked drone > > Also still present. I've described it as "they can assemble lego's > if given the instruction book -- ask them to create a lego model > without the instruction book and they are lost" > >> programmers, because they were easier to manage, interchangeable. The >> trouble was that getting an app to work took a higher level of >> understanding and skill, rather than just joining the dots. > > Yep, exactly. If they can be given instructions that match their "lego > brick set" they can snap something together. Ask them to do anything > that requires creativity or research and understanding, and you get > back a turd that has had hours of polishing applied. I feel sorry for you guys. -- Cleanse area thoroughly before applying.