Conversation

Notices

1. Embed this notice
   The Seven Voyages Of Steve (sinbad@mastodon.gamedev.place)'s status on Saturday, 25-Jan-2025 20:39:50 JST The Seven Voyages Of Steve

   This is really just a continuation of the same problem you used to get when a junior copy/pasted from Stack Overflow too much, or when they got into the habit of asking for assistance with a problem from a senior immediately, knowing they’ll solve it for them, instead of at least trying to figure it out themselves first. There are no short cuts to proper learning
   https://mastodon.sdf.org/@doragasu/113888201268209081

   • Embed this notice
     The Seven Voyages Of Steve (sinbad@mastodon.gamedev.place)'s status on Saturday, 25-Jan-2025 20:42:54 JST The Seven Voyages Of Steve

     in reply to

     Back when I was mentoring I’d often annoy a junior or two when they asked me for help, and I’d ask them what they’d already tried and if it was too little, even if I basically knew what the problem was I’d give them one pointer and make them go back and do it themselves. It’s the only way to learn

   • Embed this notice
     The Seven Voyages Of Steve (sinbad@mastodon.gamedev.place)'s status on Saturday, 25-Jan-2025 21:08:17 JST The Seven Voyages Of Steve

     in reply to

     • Peter

     @peter_sc I suspect the two things (refusal to promote learning and bad quality codebase) are linked

   • Embed this notice
     Peter (peter_sc@chaos.social)'s status on Saturday, 25-Jan-2025 21:08:20 JST Peter

     in reply to

     @sinbad I worked at a startup once where new people were told that they had exactly 15 minutes to solve a problem on their own, before they *had to* call on someone to work it out together (i.e. let the experienced guy take over). "Figuring stuff out on your own is not a good way to spend company time. You're slowing down velocity!" Mind you, this was the most bizarrely complex code base I've ever seen; layers upon layers to..ferry input from an iPad to a DB. I left after a couple of months.