Gregory's Server@saramg Wait till you get to your fifties.
|
34 comments
 @phredmoyer @sleepyfox @saramg  @sleepyfox @jannem @phredmoyer @saramg i was forced to use it by a software. At first i was amazed then i was terrified, finally i was (((((()))))) @sleepyfox @jannem @phredmoyer @saramg came here to write the very same comment. Of course: LISP.    @stonebear @jannem @phredmoyer @sleepyfox @saramg WATFOR? I ask myself what for? every time I have to use it! @Wintermute_BBS @jannem @phredmoyer @sleepyfox @saramg I can't take credit for that one. That's a line from Frank Hayes. Yeah, the one who wrote for Computerworld.  @phredmoyer @sleepyfox @saramg Pros: is right about most things Cons: can't say so without insulting everyone @saramg @schizanon @phredmoyer @sleepyfox pft! Amateurs! Iโve been doing that since I was about 14.  @schizanon @phredmoyer @sleepyfox @saramg As a 50y old software engineer. I approve of this message! @overflo @phredmoyer @sleepyfox @saramg why are we like this?  @phredmoyer @sleepyfox @saramg Iโm in my twenties, and there isnโt a single system Iโve seen that I couldnโt have written better in Perl. I would also have deleted 50% of the stack, but no one will let me. So I guess I have to wait until Iโm forty. Pros of staying around that long: Iโll be the one supposed to put up a fight when someone tries to delete 90% of the stack, and I justโฆ ๐ค wonโt. ๐  @phredmoyer @sleepyfox @saramg Cons: deletes half the stack reducing maintenance costs and why is it all Perl now? Cons: doesnโt actually know Perl but replaces the rest with Perl anyway and why is the patient data missing?  @phredmoyer @sleepyfox @saramg Do you also consider Javascript "ancient"? It was released the same year as PHP. @kevin @sleepyfox @saramg ancient was a bit of sarcasm, Iโve used Perl for 22 years. JS is still top of the red monk language roundup @phredmoyer @sleepyfox @saramg I wasn't being too serious, actually. Those languages are "old". As am I. @phredmoyer @sleepyfox @saramg The thing about "modern" languages is ... we already know that they'll be tomorrow's legacy. Feelin' sexy with your Rust and whatnot? A measly 10 years in the sun is all you get. Don't take it from me, just wait it out. "Dude look at that old fart, he's one of those 2020-era Rusties..." @phredmoyer @sleepyfox @saramg letโs be honest, Perl/php is far too modern. It would really be like Fortran or Lisp @phredmoyer @sleepyfox @saramg I think decision to use Perl/PHP as examples of "ancient languages" is what elevates this toot to a top-tier shitpost. Bravo. Seriously, well done. @sleepyfox @saramg 50s is knowing that if you rewrite the stack you'll be stuck writing code for the rest of eternity as you're beyond even your senior devs level. That sounds arrogant but honestly if you've been writing code 20+ years longer than your senior devs if you're NOT working at a different level then ๐คท  @scottgal My take was "rewrite the stack" was hyperbole for a ju-jitsu-like "make the right set of changes to dramatically change things" rather than a literal Musk "we need a total rewrite!!!" which sounds like NIH. Often that's still a challenging project, like a rewrite of a key component, but yeah, not an end-to-end rewrite. (Maybe I was overly generous in my interpretation of the post. :) @sgf Yeah I think the fancy name is 'Transformational Architecture' or less fancy 'code jenga'; changing a running app and making it better while keeping it running I think only really comes from experience. The irony is that the more able you are to manage that sort of thing the less likely you'll be in a role which allows it. @scottgal I've seen people successfully keep doing such stuff, really well, at the expense of "career advancement", but yeah. On the other hand, you get more opportunities to teach/lead others to do so. Although that's not to everyone's taste I guess. @sgf Part of it's just practical. You price yourself (either financially or skill level at stuff like architecture etc) of the 'fun' dev jobs. Staff Engineer jobs exist but they tend to be at big corps; using someone like me as a dev is EXPENSIVE when I add more value *not* writing code. @sgf Example this last go-around I applied for DOZENS of 'senior dev' jobs but the constant refrain was I was 'too experienced'...no idea if the lead thought I would be unmanageable / they though I was so old I'd croak, it never gets that far. @scottgal That seems pretty a pretty fair assessment, and I'm sorry that it sucked for you. My experience has been mostly big tech and (old-school) finance (and specifically the London market), where they can pay for experienced devs, so my view's clearly biased. |
@sleepyfox @saramg with regards to that item:
Pros: deletes half of the stack, reducing maintenance costs and making it easier to use . They would delete 90% of it, but know itโs not worth the fight.
Cons: tends to rant on about how they would have done it in ancient languages like Perl/php ;)