Here are five tips that helped me to grow as a developer.
They aren't complicated and can be implemented directly. I'm sure there is something in it for you!
🧵🔽
1️⃣ Learn To Listen
Listening is more important than talking. If someone has something to say, listen to them. Don't interrupt them. If you have questions about certain aspects of what they say, write them down. Then ask those questions later and talk about it together.
2️⃣ Accept You Don't Know Everything
Software engineering is too broad and too deep as if anyone could really know everything.
You need to accept that and understand that your peers all have their own experiences. Use this to your advantage. If you're stuck, ask for help.
3️⃣ You'll Never Catch All Corner Cases
You will never catch all possible corner cases. At some point, it's not worth it to put more thoughts into them. That's the time when you should ship your code. Sometimes, your peers find issues in reviews. Use this to your advantage.
Otherwise, make sure you are always prepared to handle errors occurring even in production. Sometimes it's easier to let it crash, analyze the issue, fix it, and then continue with your usual business.
4️⃣ Software Engineering Is A Team Game
You usually work in a team. There is no place for lone-wolves in this game. It doesn't help to blame teammates for their mistakes, and neither does it to try to hold them responsible for bad choices.
You win or fail together, as a team. It's up to you to make the best out of it, learn what happened, and ensure that it won't happen again.
If you separate yourself, you hurt your company or client more than you hurt your teammates. This will all reflect back on you.
5️⃣ Automated Testing Is Not Optional
Many beginners seem to struggle with automated testing but this is largely due to so many resources focussing on results and not on the way to achieve them.
Not knowing how to test doesn't justify leaving it out completely. Automated tests are an important safety net. If one ever fails, you know that something is wrong.
Without tests, you never know if your software is really running as it should. And clicking through a frontend,
manually, is not a great alternative either. Human work is always prone to error. Automation does always reliably and reproducibly do what you instructed it to do.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
You don't know how to get into crypto or you simply don't want to spend any money? Do you still want a piece of the cake?
Here is a short 101 on how to get your hands on some crypto and even #BTC.
🧵👇🏻
1️⃣ Download Brave
The Brave browser is based on Chromium, and designed with privacy in mind. If you are unsure, Brendan Eich (yes, exactly, him) is the CEO of Brave Software Inc., the company creating the browser.
Brave blocks ads on websites by default but it comes with its own blockchain-based ad system. Instead of putting them everywhere on websites, however, they come in the form of system notifcations, sent by your browser.
I can relate!
When I started, AWS already offered so much that I literally couldn't find an entry point.
If you still feel this way, let me give you a little guide.
🧵⏬
1️⃣ Foreword
Before we're going in, let me tell you this:
AWS is huge, and the chance that you'll ever be able to call yourself an expert in every product and service it offers is...well, low.
To be honest, I wouldn't even aim for that goal. It simply doesn't make sense. Better aim to become good at a few products and then at all the supporting ones that fit.
You'll specialize, gather deep knowledge about a few products, and be a valuable expert in that area.
Proof-Of-Work is the name of a cryptographic algorithm that is used for some blockchains when new blocks are to be appended to the chain.
Let's take a higher-level look at how this one works, shall we?
🧵🔽
1️⃣ The Basics
This algorithm creates a system in which one party (the prover) has to prove to one or multiple other parties (the verifiers) that they put in a certain amount of work for some purpose.
The work the prover has to put in is moderately hard to very hard, while the verifiers can pretty easily check whether the proof is correct. This creates an asymmetric system.
The original idea was to create protection against DDoS attacks and spam.
Svelte has topped the satisfaction rankings of "State of JS 2020" some time ago, and this justifies an introduction for everyone still not aware of it.
An introduction to Svelte 💛
🧵🔽
1️⃣ What is Svelte?
Svelte is a component-based frontend framework like React and Vue, that promises:
- Less code
- No virtual DOM
- True reactivity
and delivers on all of these pretty well.
It currently has 41.2k stars on GitHub and an active community, including 359 contributors.
The community is pretty active and unlike React, there is no huge corporation backing it.
But no need to worry, Svelte won't vanish anytime soon.
the architectural approach that makes your websites faster, safer, cheaper, and all that with a better developer experience.
🧵🔽
1️⃣ What Is It?
The Jamstack is an architectural approach.
The letters "J A M" are an acronym and actually stand for:
▶️ JavaScript
▶️ APIs
▶️ Markup
🟢 JavaScript
JavaScript is the universal runtime of the web. Every browser can handle JavaScript and it's the language that brings interactivity to every modern-day browser.
JavaScript can either be written directly or act as a compile target.
Here are _some_ of the most essential git operations you will need when working as a developer.
🧵🔽
1️⃣ Create A New Repository
This is the most basic command you'll need. When you start a repository locally, your start with git init.
2️⃣ Clone A Repository
You can clone a remote repository to get a local copy of it. Your local repository is connected to the remote one so you can pull in changes and push yours to the remote.