Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. A joke I used to tell every coöp student and early-career person I interviewed:

A joke I used to tell every coöp student and early-career person I interviewed:

Scheduled Pinned Locked Moved Uncategorized
28 Posts 17 Posters 0 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • raganwald@social.bau-ha.usR raganwald@social.bau-ha.us

    A joke I used to tell every coöp student and early-career person I interviewed:

    “We only hire senior developers. The trick is, we hire them earlier in their careers.”

    The same thing, without trying to be hip:

    “Senior engineers are what you get when you hire a junior, give them interesting problems, surround them with people who know more than they do, and wait. That's it.”

    Link Preview Image
    AI didn't kill your junior pipeline. You did | Andrew Murphy

    AI didn’t kill the junior pipeline; companies did, because someone saw Claude write a for loop and decided that meant they could stop training humans. The result is an industry cheerfully pulling the ladder up behind itself, hollowing out its seniors, and outsourcing its entire talent strategy to vendors that will eventually triple the price. If you don’t hire juniors now, don’t act surprised in five years when you’re surrounded by AI-generated code nobody understands and trying to buy senior engineers from a market everyone else forgot to replenish.

    favicon

    Andrew Murphy (andrewmurphy.io)

    timfreund@mastodon.xyzT This user is from outside of this forum
    timfreund@mastodon.xyzT This user is from outside of this forum
    timfreund@mastodon.xyz
    wrote last edited by
    #2

    @raganwald and those intern career arcs are some of the accomplishments I'm most proud of. We take a tiny chance, they do great work and launch fulfilling careers.

    raganwald@social.bau-ha.usR 1 Reply Last reply
    0
    • timfreund@mastodon.xyzT timfreund@mastodon.xyz

      @raganwald and those intern career arcs are some of the accomplishments I'm most proud of. We take a tiny chance, they do great work and launch fulfilling careers.

      raganwald@social.bau-ha.usR This user is from outside of this forum
      raganwald@social.bau-ha.usR This user is from outside of this forum
      raganwald@social.bau-ha.us
      wrote last edited by
      #3

      @timfreund I'm not a scientist, but Hammond's famous three questions for new researchers at Bell Labs seems pertinent:

      1. What's the most important open problem in your area?
      2. What are you working on?
      3. Why aren't they the same?

      1 Reply Last reply
      0
      • raganwald@social.bau-ha.usR raganwald@social.bau-ha.us

        A joke I used to tell every coöp student and early-career person I interviewed:

        “We only hire senior developers. The trick is, we hire them earlier in their careers.”

        The same thing, without trying to be hip:

        “Senior engineers are what you get when you hire a junior, give them interesting problems, surround them with people who know more than they do, and wait. That's it.”

        Link Preview Image
        AI didn't kill your junior pipeline. You did | Andrew Murphy

        AI didn’t kill the junior pipeline; companies did, because someone saw Claude write a for loop and decided that meant they could stop training humans. The result is an industry cheerfully pulling the ladder up behind itself, hollowing out its seniors, and outsourcing its entire talent strategy to vendors that will eventually triple the price. If you don’t hire juniors now, don’t act surprised in five years when you’re surrounded by AI-generated code nobody understands and trying to buy senior engineers from a market everyone else forgot to replenish.

        favicon

        Andrew Murphy (andrewmurphy.io)

        raganwald@social.bau-ha.usR This user is from outside of this forum
        raganwald@social.bau-ha.usR This user is from outside of this forum
        raganwald@social.bau-ha.us
        wrote last edited by
        #4

        My Artificially Impatient summary:

        A CEO reads a book* and "learns" that Juniors are a money sink, because the company pays them more than they are worth today, in the hopes of turning them into a Senior in the future. The CEO recognizes that in game theory, they can "defect" by hiring Seniors that other companies have trained, so they get rid of Juniors. Everyone does this because business is a pop culture, and just as game theory predicts, everyone loses.

        👇🏽

        raganwald@social.bau-ha.usR vanderzwan@vis.socialV 3 Replies Last reply
        0
        • raganwald@social.bau-ha.usR raganwald@social.bau-ha.us

          My Artificially Impatient summary:

          A CEO reads a book* and "learns" that Juniors are a money sink, because the company pays them more than they are worth today, in the hopes of turning them into a Senior in the future. The CEO recognizes that in game theory, they can "defect" by hiring Seniors that other companies have trained, so they get rid of Juniors. Everyone does this because business is a pop culture, and just as game theory predicts, everyone loses.

          👇🏽

          raganwald@social.bau-ha.usR This user is from outside of this forum
          raganwald@social.bau-ha.usR This user is from outside of this forum
          raganwald@social.bau-ha.us
          wrote last edited by
          #5

          👇🏽

          The book's* model is wrong, because Juniors perform a vital "Canary in a Coal Mine" role, and furthermore Seniors are not fungible because poaching a Senior gets you someone with vital experience and context... In somebody else's problem space.

          The correct strategy is to hire Juniors, and use the tools not to replace them, but to accelerate their path to Seniority.

          _This summary cost 3,652 Ragantokens._

          ———

          * Book, podcast, trade show, round of golf, whatever.

          1 Reply Last reply
          0
          • R relay@relay.publicsquare.global shared this topic
          • raganwald@social.bau-ha.usR raganwald@social.bau-ha.us

            My Artificially Impatient summary:

            A CEO reads a book* and "learns" that Juniors are a money sink, because the company pays them more than they are worth today, in the hopes of turning them into a Senior in the future. The CEO recognizes that in game theory, they can "defect" by hiring Seniors that other companies have trained, so they get rid of Juniors. Everyone does this because business is a pop culture, and just as game theory predicts, everyone loses.

            👇🏽

            raganwald@social.bau-ha.usR This user is from outside of this forum
            raganwald@social.bau-ha.usR This user is from outside of this forum
            raganwald@social.bau-ha.us
            wrote last edited by
            #6

            👇🏽

            That model is wrong, because Juniors perform a vital "Canary in a Coal Mine" role. And, Seniors are not fungible because poaching a Senior gets you someone with vital experience and context... In somebody else's problem space.

            The correct strategy is to hire Juniors, and use the tools not to replace them, but to make them even more productive _and_ accelerate their path to Seniority.

            _This summary cost 3,652 Ragantokens._

            ———

            * Book, podcast, trade show, round of golf, whatever.

            1 Reply Last reply
            0
            • raganwald@social.bau-ha.usR raganwald@social.bau-ha.us

              My Artificially Impatient summary:

              A CEO reads a book* and "learns" that Juniors are a money sink, because the company pays them more than they are worth today, in the hopes of turning them into a Senior in the future. The CEO recognizes that in game theory, they can "defect" by hiring Seniors that other companies have trained, so they get rid of Juniors. Everyone does this because business is a pop culture, and just as game theory predicts, everyone loses.

              👇🏽

              vanderzwan@vis.socialV This user is from outside of this forum
              vanderzwan@vis.socialV This user is from outside of this forum
              vanderzwan@vis.social
              wrote last edited by
              #7

              @raganwald I liked Ton Roosendaal's attempt at framing this (meaning the nurturing of juniors) in his 2024 keynote as "the volcano model": you make sure talent rises to the top, and in order to prevent the top from getting crowded you help (some of) them find jobs elsewhere https://www.youtube.com/watch?v=VZ5022VaMmA&t=745

              (What's even more clever about it in Blender's ca;e is that with this approach Blender becomes a cultural export to other companies)

              1 Reply Last reply
              0
              • R relay@relay.an.exchange shared this topic
              • raganwald@social.bau-ha.usR raganwald@social.bau-ha.us

                A joke I used to tell every coöp student and early-career person I interviewed:

                “We only hire senior developers. The trick is, we hire them earlier in their careers.”

                The same thing, without trying to be hip:

                “Senior engineers are what you get when you hire a junior, give them interesting problems, surround them with people who know more than they do, and wait. That's it.”

                Link Preview Image
                AI didn't kill your junior pipeline. You did | Andrew Murphy

                AI didn’t kill the junior pipeline; companies did, because someone saw Claude write a for loop and decided that meant they could stop training humans. The result is an industry cheerfully pulling the ladder up behind itself, hollowing out its seniors, and outsourcing its entire talent strategy to vendors that will eventually triple the price. If you don’t hire juniors now, don’t act surprised in five years when you’re surrounded by AI-generated code nobody understands and trying to buy senior engineers from a market everyone else forgot to replenish.

                favicon

                Andrew Murphy (andrewmurphy.io)

                numodular@c.imN This user is from outside of this forum
                numodular@c.imN This user is from outside of this forum
                numodular@c.im
                wrote last edited by
                #8

                @raganwald Apropos for the ultra-processed food industry, in artificial #USpol

                "Early career", meet #EmergingEconomies in #DevelopingCountries, where organic includes well-rooted origins. Makes for a better trajectory than the precipitous fall, the US is championing.

                1 Reply Last reply
                0
                • raganwald@social.bau-ha.usR raganwald@social.bau-ha.us

                  A joke I used to tell every coöp student and early-career person I interviewed:

                  “We only hire senior developers. The trick is, we hire them earlier in their careers.”

                  The same thing, without trying to be hip:

                  “Senior engineers are what you get when you hire a junior, give them interesting problems, surround them with people who know more than they do, and wait. That's it.”

                  Link Preview Image
                  AI didn't kill your junior pipeline. You did | Andrew Murphy

                  AI didn’t kill the junior pipeline; companies did, because someone saw Claude write a for loop and decided that meant they could stop training humans. The result is an industry cheerfully pulling the ladder up behind itself, hollowing out its seniors, and outsourcing its entire talent strategy to vendors that will eventually triple the price. If you don’t hire juniors now, don’t act surprised in five years when you’re surrounded by AI-generated code nobody understands and trying to buy senior engineers from a market everyone else forgot to replenish.

                  favicon

                  Andrew Murphy (andrewmurphy.io)

                  emc2@indieweb.socialE This user is from outside of this forum
                  emc2@indieweb.socialE This user is from outside of this forum
                  emc2@indieweb.social
                  wrote last edited by
                  #9

                  @raganwald

                  Words that stick in my head: always look at what someone could become with the right support and guidance.

                  raganwald@social.bau-ha.usR 1 Reply Last reply
                  0
                  • emc2@indieweb.socialE emc2@indieweb.social

                    @raganwald

                    Words that stick in my head: always look at what someone could become with the right support and guidance.

                    raganwald@social.bau-ha.usR This user is from outside of this forum
                    raganwald@social.bau-ha.usR This user is from outside of this forum
                    raganwald@social.bau-ha.us
                    wrote last edited by
                    #10

                    @emc2 From when I was in leadership:

                    "What could this team accomplish if I got the rest of the org out the fuck of their way?"

                    1 Reply Last reply
                    0
                    • raganwald@social.bau-ha.usR raganwald@social.bau-ha.us

                      A joke I used to tell every coöp student and early-career person I interviewed:

                      “We only hire senior developers. The trick is, we hire them earlier in their careers.”

                      The same thing, without trying to be hip:

                      “Senior engineers are what you get when you hire a junior, give them interesting problems, surround them with people who know more than they do, and wait. That's it.”

                      Link Preview Image
                      AI didn't kill your junior pipeline. You did | Andrew Murphy

                      AI didn’t kill the junior pipeline; companies did, because someone saw Claude write a for loop and decided that meant they could stop training humans. The result is an industry cheerfully pulling the ladder up behind itself, hollowing out its seniors, and outsourcing its entire talent strategy to vendors that will eventually triple the price. If you don’t hire juniors now, don’t act surprised in five years when you’re surrounded by AI-generated code nobody understands and trying to buy senior engineers from a market everyone else forgot to replenish.

                      favicon

                      Andrew Murphy (andrewmurphy.io)

                      G This user is from outside of this forum
                      G This user is from outside of this forum
                      gbsills@social.vivaldi.net
                      wrote last edited by
                      #11

                      @raganwald This was good. When I first interacted with GitHub Copilot, I felt it was like an automated junior developer without an ability to get better. This includes Copilot cutting an pasting code found on StackOverflow and GitHub, just like a junior developer. So, of course, business guys would decide "hey, we can just hire a senior guy to code review the AI code. What could go wrong?"

                      And no, other AI coding tools are not any better.

                      raganwald@social.bau-ha.usR 1 Reply Last reply
                      0
                      • G gbsills@social.vivaldi.net

                        @raganwald This was good. When I first interacted with GitHub Copilot, I felt it was like an automated junior developer without an ability to get better. This includes Copilot cutting an pasting code found on StackOverflow and GitHub, just like a junior developer. So, of course, business guys would decide "hey, we can just hire a senior guy to code review the AI code. What could go wrong?"

                        And no, other AI coding tools are not any better.

                        raganwald@social.bau-ha.usR This user is from outside of this forum
                        raganwald@social.bau-ha.usR This user is from outside of this forum
                        raganwald@social.bau-ha.us
                        wrote last edited by
                        #12

                        @gbsills Putting my technical product manager hat on top of my product design hat, if I can ethically do 4x the delivery, I would rather ship four variations of one feature behind feature flags and test the results, than ship four features serially and be too busy shipping the next four to review the results of my experiments.

                        G 1 Reply Last reply
                        0
                        • raganwald@social.bau-ha.usR raganwald@social.bau-ha.us

                          @gbsills Putting my technical product manager hat on top of my product design hat, if I can ethically do 4x the delivery, I would rather ship four variations of one feature behind feature flags and test the results, than ship four features serially and be too busy shipping the next four to review the results of my experiments.

                          G This user is from outside of this forum
                          G This user is from outside of this forum
                          gbsills@social.vivaldi.net
                          wrote last edited by
                          #13

                          @raganwald Yeah, it is hard for product managers to withstand the pressure to release product quickly. Often, phrases like "shipped on xx/xx/xxxx" and the development run rate $$$ is the only thing the people above them understand.

                          raganwald@social.bau-ha.usR 1 Reply Last reply
                          0
                          • G gbsills@social.vivaldi.net

                            @raganwald Yeah, it is hard for product managers to withstand the pressure to release product quickly. Often, phrases like "shipped on xx/xx/xxxx" and the development run rate $$$ is the only thing the people above them understand.

                            raganwald@social.bau-ha.usR This user is from outside of this forum
                            raganwald@social.bau-ha.usR This user is from outside of this forum
                            raganwald@social.bau-ha.us
                            wrote last edited by
                            #14

                            @gbsills I have spent 25+ years advocating for feedback loops. My go-to slides compared a ballistic approach to air travel (aim very carefully and take EVERYTHING into account at fine levels of detail, then launch and pray) versus flying the aircraft (continuous adjustments in flight).

                            Got me respect, but in a crunch leadership would... Go ballistic.

                            1 Reply Last reply
                            0
                            • raganwald@social.bau-ha.usR raganwald@social.bau-ha.us

                              A joke I used to tell every coöp student and early-career person I interviewed:

                              “We only hire senior developers. The trick is, we hire them earlier in their careers.”

                              The same thing, without trying to be hip:

                              “Senior engineers are what you get when you hire a junior, give them interesting problems, surround them with people who know more than they do, and wait. That's it.”

                              Link Preview Image
                              AI didn't kill your junior pipeline. You did | Andrew Murphy

                              AI didn’t kill the junior pipeline; companies did, because someone saw Claude write a for loop and decided that meant they could stop training humans. The result is an industry cheerfully pulling the ladder up behind itself, hollowing out its seniors, and outsourcing its entire talent strategy to vendors that will eventually triple the price. If you don’t hire juniors now, don’t act surprised in five years when you’re surrounded by AI-generated code nobody understands and trying to buy senior engineers from a market everyone else forgot to replenish.

                              favicon

                              Andrew Murphy (andrewmurphy.io)

                              notyoursysadmin@infosec.exchangeN This user is from outside of this forum
                              notyoursysadmin@infosec.exchangeN This user is from outside of this forum
                              notyoursysadmin@infosec.exchange
                              wrote last edited by
                              #15

                              @raganwald I think it's very important for us to take lessons from the manufacturing industry here. In the US at least, it's incredibly difficult to make anything domestically. Complicating things further, a Smarter Every Day video from several months ago found that, not only have we lost the ability to make things, we've lost the ability to make the things that make things. In his case, he found that finding folks who knew how to make the molds and metal stamping components was difficult to impossible to find domestically.

                              And we're gladly walking into the same trap with knowledge work. It isn't enough that we're outsourcing software development itself. We're outsourcing the ability to make new software engineers. (And, being an Ops person, I'd argue that we're doing that with all knowledge-based roles in general.)

                              1 Reply Last reply
                              0
                              • raganwald@social.bau-ha.usR raganwald@social.bau-ha.us

                                A joke I used to tell every coöp student and early-career person I interviewed:

                                “We only hire senior developers. The trick is, we hire them earlier in their careers.”

                                The same thing, without trying to be hip:

                                “Senior engineers are what you get when you hire a junior, give them interesting problems, surround them with people who know more than they do, and wait. That's it.”

                                Link Preview Image
                                AI didn't kill your junior pipeline. You did | Andrew Murphy

                                AI didn’t kill the junior pipeline; companies did, because someone saw Claude write a for loop and decided that meant they could stop training humans. The result is an industry cheerfully pulling the ladder up behind itself, hollowing out its seniors, and outsourcing its entire talent strategy to vendors that will eventually triple the price. If you don’t hire juniors now, don’t act surprised in five years when you’re surrounded by AI-generated code nobody understands and trying to buy senior engineers from a market everyone else forgot to replenish.

                                favicon

                                Andrew Murphy (andrewmurphy.io)

                                cdonat@hostsharing.coopC This user is from outside of this forum
                                cdonat@hostsharing.coopC This user is from outside of this forum
                                cdonat@hostsharing.coop
                                wrote last edited by
                                #16

                                @raganwald

                                At the same time those same companies tell seniors looking for a new job, that they're too old. Not flexible enough.

                                Kept up to date for decades in one of the fastest changing industries. Not flexible enough. Sure!

                                Developed the current technologies, but not flexible enough to use them in their work now. Sure!

                                Like they think, they don't need software developers at all any more. They're wrong, but sadly confident.

                                1 Reply Last reply
                                0
                                • raganwald@social.bau-ha.usR raganwald@social.bau-ha.us

                                  A joke I used to tell every coöp student and early-career person I interviewed:

                                  “We only hire senior developers. The trick is, we hire them earlier in their careers.”

                                  The same thing, without trying to be hip:

                                  “Senior engineers are what you get when you hire a junior, give them interesting problems, surround them with people who know more than they do, and wait. That's it.”

                                  Link Preview Image
                                  AI didn't kill your junior pipeline. You did | Andrew Murphy

                                  AI didn’t kill the junior pipeline; companies did, because someone saw Claude write a for loop and decided that meant they could stop training humans. The result is an industry cheerfully pulling the ladder up behind itself, hollowing out its seniors, and outsourcing its entire talent strategy to vendors that will eventually triple the price. If you don’t hire juniors now, don’t act surprised in five years when you’re surrounded by AI-generated code nobody understands and trying to buy senior engineers from a market everyone else forgot to replenish.

                                  favicon

                                  Andrew Murphy (andrewmurphy.io)

                                  zimzat@mastodon.socialZ This user is from outside of this forum
                                  zimzat@mastodon.socialZ This user is from outside of this forum
                                  zimzat@mastodon.social
                                  wrote last edited by
                                  #17

                                  This likens back to Netflix (circa 2014) showing they rarely hire Interns/Juniors, to which someone gave a memorable response in the form of "If you don't hire juniors, you don't deserve seniors" in 2018. https://dev.to/isaacdlyman/if-you-dont-hire-juniors-you-dont-deserve-seniors-48kb

                                  The industry has been making moves to avoid hiring Juniors, or training _anyone_, for a long time under the assumption someone else will do it or everyone will "sink or swim" on their own (externalizing the cost to individuals).

                                  @raganwald

                                  zimzat@mastodon.socialZ 1 Reply Last reply
                                  0
                                  • zimzat@mastodon.socialZ zimzat@mastodon.social

                                    This likens back to Netflix (circa 2014) showing they rarely hire Interns/Juniors, to which someone gave a memorable response in the form of "If you don't hire juniors, you don't deserve seniors" in 2018. https://dev.to/isaacdlyman/if-you-dont-hire-juniors-you-dont-deserve-seniors-48kb

                                    The industry has been making moves to avoid hiring Juniors, or training _anyone_, for a long time under the assumption someone else will do it or everyone will "sink or swim" on their own (externalizing the cost to individuals).

                                    @raganwald

                                    zimzat@mastodon.socialZ This user is from outside of this forum
                                    zimzat@mastodon.socialZ This user is from outside of this forum
                                    zimzat@mastodon.social
                                    wrote last edited by
                                    #18

                                    The idea that Juniors only exist to write boilerplate has always been wrong; similarly the idea we should use AI to generate boilerplate ignores the fact that boilerplate, by and large, should not exist. It is a sign of a bad abstraction, an inefficient protocol, an outdated model, a code base stuck in the mud, or management blocking enhancements. We don't need ways to generate it faster; we need to engineer ways to avoid it entirely.

                                    @raganwald

                                    zimzat@mastodon.socialZ 1 Reply Last reply
                                    0
                                    • zimzat@mastodon.socialZ zimzat@mastodon.social

                                      The idea that Juniors only exist to write boilerplate has always been wrong; similarly the idea we should use AI to generate boilerplate ignores the fact that boilerplate, by and large, should not exist. It is a sign of a bad abstraction, an inefficient protocol, an outdated model, a code base stuck in the mud, or management blocking enhancements. We don't need ways to generate it faster; we need to engineer ways to avoid it entirely.

                                      @raganwald

                                      zimzat@mastodon.socialZ This user is from outside of this forum
                                      zimzat@mastodon.socialZ This user is from outside of this forum
                                      zimzat@mastodon.social
                                      wrote last edited by
                                      #19

                                      The expectation that folks will learn by osmosis feels like we're continuing to avoid the elephant in the room: The continued lack of regulations, standards, certifications, professional associations, and unions means "Senior Software Engineer" has no actual meaning beyond vibes and feels and we are long past the point where that needs to change. We don't engineer buildings based on vibes, nor should software.

                                      @raganwald

                                      zimzat@mastodon.socialZ ryencode@mstdn.caR 2 Replies Last reply
                                      0
                                      • zimzat@mastodon.socialZ zimzat@mastodon.social

                                        The expectation that folks will learn by osmosis feels like we're continuing to avoid the elephant in the room: The continued lack of regulations, standards, certifications, professional associations, and unions means "Senior Software Engineer" has no actual meaning beyond vibes and feels and we are long past the point where that needs to change. We don't engineer buildings based on vibes, nor should software.

                                        @raganwald

                                        zimzat@mastodon.socialZ This user is from outside of this forum
                                        zimzat@mastodon.socialZ This user is from outside of this forum
                                        zimzat@mastodon.social
                                        wrote last edited by
                                        #20

                                        The reality is that most software problems are solved; what we're doing is failing to disseminate the solutions as best practices because we rely on word-of-mouth. Companies expect developers to learn on their own time while also running everyone at 120% capacity with deadlines of "due: yesterday" give no time to fix anything and denying any autonomy... and then individual growth becomes stunted.

                                        ¯\_(ツ)_/¯

                                        @raganwald

                                        1 Reply Last reply
                                        0
                                        • raganwald@social.bau-ha.usR raganwald@social.bau-ha.us

                                          A joke I used to tell every coöp student and early-career person I interviewed:

                                          “We only hire senior developers. The trick is, we hire them earlier in their careers.”

                                          The same thing, without trying to be hip:

                                          “Senior engineers are what you get when you hire a junior, give them interesting problems, surround them with people who know more than they do, and wait. That's it.”

                                          Link Preview Image
                                          AI didn't kill your junior pipeline. You did | Andrew Murphy

                                          AI didn’t kill the junior pipeline; companies did, because someone saw Claude write a for loop and decided that meant they could stop training humans. The result is an industry cheerfully pulling the ladder up behind itself, hollowing out its seniors, and outsourcing its entire talent strategy to vendors that will eventually triple the price. If you don’t hire juniors now, don’t act surprised in five years when you’re surrounded by AI-generated code nobody understands and trying to buy senior engineers from a market everyone else forgot to replenish.

                                          favicon

                                          Andrew Murphy (andrewmurphy.io)

                                          0x4d6165@transfem.social0 This user is from outside of this forum
                                          0x4d6165@transfem.social0 This user is from outside of this forum
                                          0x4d6165@transfem.social
                                          wrote last edited by
                                          #21

                                          @raganwald@social.bau-ha.us "Every senior engineer alive today got their start doing the exact grunt work they're now saying juniors don't need to do. That's not progress. That's pulling the ladder up behind you."

                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          • Login

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • World
                                          • Users
                                          • Groups