As a jr. dev who recently changed careers from something else technical to web development I have a bit of a concern about how the attributes of a jr. dev in web development are often portrayed as inherently negative. I feel like I see this far more in the development space compared to my past career (networking). This is just my impression, i'm a n00b, so I'm not at all sure how widespread it is.
In the networking land if I saw someone's messed up VLAN config I'd sit down with them "Hey man I see what I think you wanted to do, let's talk about what we want to do here and some other ways to get you what you wanted here."
In the dev world (particularly online) I often see citations about something silly jr. dev does as just being "bad", but those things are what people do... while they're learning to do it better. So some guy fires up create react app to quickly put together an app, maybe he didn't have to, maybe it was somewhat less efficient to use CRA, but in doing so he learns a ton about react outside of the scaffolding and etc. Being a not so great dev is also what you do while learning to be better.
I'm not at all sure if the purpose of these Koans here so maybe I'm off topic, but that's just an observation of mine.
Something like 2-3 years ago I've read similar thing with master foo but about git. Does anyone happen to know where I can find it? I've searched for it but failed to find :(
The young disciple entered the temple and prostrated 3 times before the master and asked - "I wish to know the way of Microservices. I wish to glean insight on how to build them as it will let us scale and build rapidly".
The master jumped off his chair and landed head-first on the floor.
"What happened!" ask the disciple.
"I'm learning how to sky dive" replied the master.
I only wish there were more. I have been thinking a lot about junior developers and how to meet them where they are. Once you've been around the block a few times it is hard to put yourself in that mindset, but in order to help them be effective and efficient (and to keep them around) it seems like you have to.
Mentor/student is not the same dynamic as lead/junior.
As both lead and mentor simultaneously to a junior developer, the suggestions I give him are very _very_ different depending on which role I'm playing at the time, and I make it abundantly clear which role is speaking at any given point in time.
This is precisely the sort of suggestion many juniors need to hear from their mentors (because there is real value in understanding the difference between deep and shallow knowledge, and the role of tooling), but is of course a terrible task for a lead to give a junior (because it's a pointless waste of time as part of a production project)
There are teams, that don't need to use scaffolding provided by "create-react-app". Maybe they just need a small react powered widget on their site, it would be silly to scaffold whole separate project just for that widget. Also, if you are using React as your primary tool, you should actually know, how to set it up manually.
[+] [-] llamataboot|7 years ago|reply
"Break it up" the teacher instructed.
And so the student broke the monolith into many pieces, and then became confused by how all the pieces fit together.
"Put it back together" the teacher instructed.
And so the student rebuilt the monolith, fat controllers and all, but she was not scared, neither of the many pieces, nor the size.
[+] [-] duxup|7 years ago|reply
In the networking land if I saw someone's messed up VLAN config I'd sit down with them "Hey man I see what I think you wanted to do, let's talk about what we want to do here and some other ways to get you what you wanted here."
In the dev world (particularly online) I often see citations about something silly jr. dev does as just being "bad", but those things are what people do... while they're learning to do it better. So some guy fires up create react app to quickly put together an app, maybe he didn't have to, maybe it was somewhat less efficient to use CRA, but in doing so he learns a ton about react outside of the scaffolding and etc. Being a not so great dev is also what you do while learning to be better.
I'm not at all sure if the purpose of these Koans here so maybe I'm off topic, but that's just an observation of mine.
[+] [-] theyoungwolf|7 years ago|reply
[+] [-] teddyh|7 years ago|reply
The Tao of Programming:
https://en.wikipedia.org/wiki/The_Tao_of_Programming
Rootless Root — The Unix Koans of Master Foo:
http://www.catb.org/~esr/writings/unix-koans/
And lastly, The Tao Of Backup:
http://www.taobackup.com/
[+] [-] Exorus18|7 years ago|reply
[+] [-] statictype|7 years ago|reply
The master jumped off his chair and landed head-first on the floor.
"What happened!" ask the disciple.
"I'm learning how to sky dive" replied the master.
Upon hearing this, the disciple was enlightened.
[+] [-] ravedave5|7 years ago|reply
[+] [-] cstuder|7 years ago|reply
http://thecodelesscode.com/contents
[+] [-] jacobush|7 years ago|reply
[+] [-] bigbadgoose|7 years ago|reply
http://catb.org/jargon/html/koans.html
[+] [-] stoksc|7 years ago|reply
[+] [-] brootstrap|7 years ago|reply
[+] [-] mooreds|7 years ago|reply
[+] [-] sevensor|7 years ago|reply
[+] [-] unknown|7 years ago|reply
[deleted]
[+] [-] _pmf_|7 years ago|reply
> The student could not.
He could, how ever, BCC his team lead's boss that he's being put on useless tasks that only serve to give the team lead a sense of superiority.
[+] [-] pdpi|7 years ago|reply
As both lead and mentor simultaneously to a junior developer, the suggestions I give him are very _very_ different depending on which role I'm playing at the time, and I make it abundantly clear which role is speaking at any given point in time.
This is precisely the sort of suggestion many juniors need to hear from their mentors (because there is real value in understanding the difference between deep and shallow knowledge, and the role of tooling), but is of course a terrible task for a lead to give a junior (because it's a pointless waste of time as part of a production project)
[+] [-] dijit|7 years ago|reply
Frankly I welcome someone who wants to teach me something I don’t know. As long as they’re not obnoxious (which is, thankfully, rare)
[+] [-] jyriand|7 years ago|reply