Junior developer survival tips (with Mayuko)
Вставка
- Опубліковано 14 лип 2024
- 💛 X-team (Episode sponsor)
x-team.com/fff
X-Team offers remote work for developers. They partner up with high-profile companies and help them scale their development teams.
💛 Fun Fun Forum discussion topic for this video
www.funfunforum.com/t/surviva...
💛 Mayuko's UA-cam channel
• Dealing with Conflict ...
💛 ”Nothing Works” by Jack Conte, a talk about failure:
• Video
💛 The x y problem
xyproblem.info
💛 Follow on Twitch and support by becoming a Subscriber
We record the show live Mondays 7 AM PT
/ funfunfunction
💛 Fun Fun Forum
Private discussion forum with other viewers in between shows. www.funfunforum.com. Available to patron members, become one at / funfunfunction
💛 mpj on Twitter
/ mpjme
💛 CircleCI (Show sponsor)
Robust and sleek Docker-based Continuous Integration as a service. I used CircleCI prior to them becoming a sponsor and I love that their free tier is powerful enough for small personal projects, even if they are private. Use this link when you sign up to let them know you came from here:
circleci.funfunfunction.com
💛 Quokka (Show sponsor)
Wonder how MPJ evaluates JavaScript inline his editor. Quokka is the answer - use this link when you buy to let them know you came from here:
quokka.funfunfunction.com
💛 Wallaby (Show sponsor)
Wallaby.js runs your JavaScript tests immediately as you type and displays execution results in your code editor. It is insanely fast, because it only executes tests affected by your code changes and runs tests in parallel. Let them know you came from us by using this link:
wallaby.funfunfunction.com
💛 FUN FUN FUNCTION
Since 2015, Fun Fun Function (FFF) is one of the longest running weekly UA-cam shows on programming 🏅 thanks to its consistency and quality reaching 200,000+ developers.
🤦♂️ The Failing Together concept is what makes FFF unique. Most coding content out there focus on step-by-step tutorials. We think tutorials are too far removed from what everyday development is like. Instead, FFF has created a completely new learning environment where we grow from failure, by solving problems while intensively interacting with a live audience.
Tutorials try to solve a problem. Failing Together makes you grow as a developer and coworker.
📹 Each show is recorded live on Twitch in a 2-hour livestream on Mondays. The host, assisted by the audience, is tasked to complete a programming challenge by an expert guest. Like in the real world, we often fail, and learn from it. This, of course, reflects what the audience identifies with, and is one of the most praised aspects of the show.
⏯ On Fridays, an edited version of the show is adapted for and published on UA-cam.
Content Topics revolve around: JavaScript, Functional Programming, Software Architecture, Quality Processes, Developer Career and Health, Team Collaboration, Software Development, Project Management - Наука та технологія
Very useful tips! I've personally noticed the "ask a lot of questions" tip in practice and it's definitely true. The hardest part for me is that I don't want to bother the senior developers too often since they have plenty of work on their own plate and I feel like it's very frustrating if some new developer comes back to you every other 5 minutes with a small question. Usually I get stuck at lots of different steps of the learning process since I'm so very new at all these things. Often I try googling solutions, but in most cases I just need some direct feedback to help me along. I still try to ask questions regularly, but I still really have to force myself.
Not asking question at right time in the beginning was the problem I suffered. This video is great and very relatable.
Make another video for how junior can transition to advanced level
+1
By continuing to code and apply everything you learn, which causes you to continue to learn. You can only go so far if you're not going to apply what you learn. Basically, use it or lose it.
The problem with advanced level is defining advanced level(s). In the industry, generally speaking, progressing to an advanced level is just assuming more responsibility for your product.
Follow these 3 principles: get good, get great, get better
Perfect timing for this video! Thanks for sharing
Very relatable video, 6 months into my first developer job here!
Thanks for the tips so useful, I'm a Junior Dev and constantly battling the concept of not knowing everything straight away or when I expect to and understanding that that's normal in this profession and it's okay to fail:-D
Around 7 minutes in Mayuko talks about 'failing well'. It's a great point.
First one because I follow you both guys
computer programming was once mostly a female profession, as it was popularly viewed as an extension of secretarial duties. Later, it was considered a form of engineering, and thus better suited to men. Finally, the numbers of each gender in the profession are (very gradually) moving towards parity.
well, those kind of jobs back then, were also really really simple programming tasks, as companies didn't actually know what IT were capable off. My mother had a similar job back then. There were however really complex jobs for engineers as well.
My first development job was horrible.
I was so inexperienced that it felt like asking so many questions would basically just be having someone else do my job.
My boss wasn't exactly a patient person either, quite quick-tempered and high expectations.
The stress of working there had me develop trichotillomania which I actually still struggle with when I get severely stressed but I think I handle it a bit better.
It can be very stressful being a junior dev.
I'm a bit worried about my brother in law who I think could be in a similar position.
They have him not just doing all the development work but IT & infrastructure work too and he's only just out of university.
I sometimes help him out at lunch over facebook when he asks, but I'm trying to encourage him to look for a better job, one that actually has a team.
I feel like coming out of university there should be a warning that if you're working on your own then there is too much responsibility placed on you.
This is me right now
@@gracechiamaka4668 It makes all the difference when you actually have a good team behind you.
It turned from, "I have to learn absolutely everything on my own"
to your team working with what you do know and giving you more simple manageable tasks to work on.
Which can allow you to learn as you go and feel like you're contributing to the team.
They may even just put you straight onto training if it's a well-established company with their processes.
It's pretty scary to ask senior developers questions, i risk myself getting fired.
I asked a few questions to a manager once when I got interviewed for a role. I got hired on the spot. I got taken off the project that evening for asking some questions.
On the topic of Mr. Opinion Man
In a previous company I worked at if you didn't speak with absolute certainty you didn't get listened to,
They did listen to a fully confident developer yet naiive in the area I was trying to give an opinion on.
They didn't know all the ins and outs but because I was weighing up the potential problems I was seen as someone who just didn't know very much xD
My survival tipps:
- breath
- ask people for ressources(water access, food, shelter) (you might get some friends even)
- have your mission and you follow through
- don't let the environment bring you down if it wants to put weird illusions on you (even if they are most common ones like: "you need money to survive" - no you don't. Moreseo you need these tipps)
You are more free this way then wasting your time to work for money.
We who can think outside of the illusions - might not want to waste our time that way.
We might have our own illusion in which we know exactly how we can repair the world.
And from my experience my illusion I have about it. That is in conflict to most any paths one would go when first going for money.
Oh Nice collabo!
For some time, I am trying to learn front-end web development only from online sources, i.e. without a course, well I use a freecodecamp and other sources, but I wonder if it is even possible to become a good front-end web developer this way. recently, I feel a bit like I hit the wall. And now I am also thinking how to get to the stage junior from that point...
A way to make yourself a bit more comfortable asking stupid questions is just call yourself out on it before starting. I mean, start with "Hey, stupid question incoming, but ....". As much as I would like to provide a reasonable explanation as to why this works, I really can't, but it does. And straight up think logically about the situation, because the fact of the matter is that you're there, you don't know the answer to that question, but knowing it is important for you to be able to make yourself useful, thus by asking, you're making an effort to make yourself useful, and nobody can judge you for that.
My first development job IS on a radiotherapy app using Laravel+React+Python+Java... This is what 'scary' really means kk' I was completely lost at the start kk'
My first job was awful, the comapny was awful.. in the sense there was no Lead.. I had to learn angularJS and there was no one else to mentor / teach me that. I just learned all the bad things I could in that company without structure...
i had a very similar experience, junior dev thrust into jquery/angularJS with no lead
Mayuko never curses on her channel but I think you made her comfortable enough to do it on your channel
Mayuko needs better lighting and MPJ needs better sound^^
const LikedBeforeWatching = true;
she's using so many 'like' word, it's annoying