Photo by Katrina Wright on Unsplash
What to say, these are strange times we live in at the moment.
We need to stay safe and be positive.
I read some excellent articles in March, and hopefully, you'll find them beneficial.
Every sufficiently interesting game has a metagame above it. This is the game about the game. It is often called 'the meta'.
Every sufficiently interesting domain in the world has a meta associated with it.
What is interesting about the meta is that metagames can only be played if you have mastered the basics of the domain. In MtG, Judo, and Splendor, you cannot play the metagame if you are not already good at the base game. You cannot identify winning strategies in MtG if you don't do well in current MtG; you cannot adapt old techniques to new rules if you don't already have effective techniques for competitive Judo.
How do you balance between locating the meta and chasing boring fundamentals? The short answer to that is to do trial and error. If you can't master a particular skill, drop back down to its component elements and practice each of them in isolation. If you don't get good conversions in your content marketing, drop down to practice publishing at a regular cadence. If you can't get a throw to work, break it down to arms, then legs, then body position, then into one complete motion.
Companies want a — DevOps, technical architect, public speaker wizard, sales, marketing professional data scientist system admin, TechOps, requirements manager, excel expert, leader, SAAS expert, cloud certified expert all rolled into one. Is it really a shortage issue or an expectation problem?
You do not always need star programmers, but you need developers with a good mental attitude willing to evangelize the company's vision
The reality that we all need to accept, a job posting doesn't describe a real person. It describes a fictional and often unrealistic ideal that most companies won't find
- "Refactoring will reduce the volatility in the marginal cost of features"
- "In the last 3 months, we spent 63% of development budget in fixing quality issues"
- "We took technical loans to ship faster, we need to pay back some debt to keep a low time-to-market"
- "We can reduce our turnover by investing 10% of our time in our code quality"
- "Investing 20% of budget in refactoring will cut FRT in half with a positive ROI on devs productivity"
- You don't need to learn every new thing in order to stay relevant.
- Writing good code takes less time than writing bad code, BUT it doesn't feel that way.
- Working 24/7 does NOT make you a hero. Managing expectations does.
- Not all time spent "improving" code has the same ROI.
- Scheduled down time makes you more productive.
- Favor verbosity over brevity
- Survey results
- Late December or early January prediction posts
- Trends and newest courses from training providers
- Meetups and your social/professional circle
- Google alerts
- GitHub explore
- Infoq reports
- Summaries from blog platforms
- Twitter trends (or trends from other social media)
In my case, I have tried to become a super developer and became super burnout instead. I repeat again: hard work is what you need to achieve success and become a good developer. However, hard work is not the only ingredient. It is part of a much bigger recipe.
Stop listening to all those people telling you that they code in their sleep, that they listen to ten podcasts per day, that they are this and that. Most of them are role-playing. Be assured that they do not do what they preach.
Be patient, be consistent, be curious, and you can become an excellent developer, and also have a beautiful life. Always remember that life is more than just work, and programming.
- Women Who Code
- SitePoint Community
- Indie Hackers
- Code Newbie
- Digital Ocean Community
- Product Hunt
- The Interaction Design Foundation Community
- Daily UI
- DevRel Collective
- Facebook Developer Circles
- Google Developers Groups
It's easy to become overwhelmed by all of the informations and advice you read or hear. It's easy to feel inadequate, and to push yourself hard to try to become that person. But don't worry.
All of this is bullshit.
The perfect career is the one that is in line with your values. Do not compare you career to anyone else's. We are all different, and our goals will always differ. And you can't compare the chapter 2 of your story to a chapter 23 of another developer's story.
- Find people who inspire you, but don't idolize them
- Don't devalue your work
- Don't feel pressured to work all the time
- Ignore fluff
- Dig into past research
- Take on big projects. Get uncomfortable
- Learn C
- Write a compiler
- Learn macros
- Understand continuations
- If anything, just try a new language
Thank you for reading, spread positivity!