Before we start - I'm working on https://cloudash.dev, a brand new way of monitoring serverless apps 🚀. Check it our if you're tired of switching between 50 CloudWatch tabs when debugging a production incident.
A short while ago I've tweeted a following question:
Tomasz ŁakomyWhat’s the best tweet sized lesson you’ve learned in your programming career?23:12 PM - 05 Jan 2020
Quite a few of developers from various background decided to share their lessons learned in the Twitter thread and I'd like to share some of them with the dev.to community
1) "Experience comes with time and practice" - Ania
Ania Wsz@aniawsz@tlakomy Experience comes with time and practice and can’t be substituted with memorized concepts and syntax. So relax, learn how to use the docs and search for information, read other people’s code. Enjoy the ride, you’re doing great 👌09:35 AM - 06 Jan 2020
2) "There is no magic happening in the programming world" - Xiaoru Li
Leo || Xiaoru Li@tlakomy There is no magic happening in the programming world
I've come across many tools, libs, concepts that I felt so advanced that they were like magic to me. I therefore fear and procrastinate learning how they actually work
Turns out if I put in effort, any "magic" can be mastered00:19 AM - 06 Jan 2020
3) "When things go wrong, blame the process, not people." - Sophie
4) "Manually verify things you’re very sure to be true" - Jamon
Jamon Holmgren@tlakomy When you’re struggling with a particularly stubborn bug, always manually verify things you’re very sure to be true. It often turns out to not be what you expect.
twitter.com/jamonholmgren/…07:47 AM - 06 Jan 2020Jamon Holmgren @jamonholmgrenWhen I pair with one of my devs to help them with a stubborn failing test, the first thing I do is change the test to `expect(true).toBe(true)`. If the test then passes, then we're working in the right file. That's step one. 😅
5) "Software is not the goal, it is the by-product" (I absolutely love this one by the way) - Adri
𝔸𝕕𝕣𝕚 𝔽𝕠𝕟𝕥𝕔𝕦@afontq@tlakomy Software is not the goal, it is the by-product. This is not about writing software, this is about providing value.23:38 PM - 05 Jan 2020
7) "Make your worst-case estimation for the time you need to solve the problem, double it, and you'll have a realistic timeline." - Olena
8) "Always back up your database. Always verify that your backups work." - Harper
Harper Maddox 🧢@harpermaddox@tlakomy Always back up your database. Always verify that your backups work.23:39 PM - 05 Jan 2020
9) "“When you became master in one thing, it’s time to become a student in another”" - Marc
𝙼𝚊𝚛𝚌 𝙱𝚊𝚌𝚔𝚎𝚜 ⚡️@_marcba@tlakomy “When you became master in one thing, it’s time to become a student in another”
(Part of a speech given at my master’s graduation ceremony)05:16 AM - 06 Jan 2020
Piotr Monwid-Olechnowicz@tlakomy Stop caring about best practices and cool patterns. Strive for deeper understanding. Notice trade-offs. Get accustomed with trade-offs in your field. Bring value. Solve problems. Read other ppl’s code (other teams in yr co and OSS). Learn in public. Be a +10% engineer.09:02 AM - 06 Jan 2020
If you're on Twitter, I highly recommend you follow all of those amazing people.
By the way, what are your lessons learned in your career?