Mistakes I made as a software engineer (developer)...
A Thread...
It’s okay to screw up — that’s how you learn and grow. But, be sure to learn from past mistakes.
Every software engineer has their own quirks.
▫ I assumed that documentation is not needed.
Biggest mistake ever.
Create a Wiki/Confluence page for your project and write down everything.
For e.g.
If your project requires access to a database, write down the how-to setup on the Wiki page.
You’ll be very happy when a new teammate joins and you point them to the Wiki page with everything written down.
▫ I give up too soon.
We’re all victims of giving up too soon — after all, it’s much easier to just give up.
But you know a developer accomplished many impossible things by doing, and not by giving up.
This reminds me: 👇
“I’m convinced that about half of what separates successful entrepreneurs from the non-successful ones is pure perseverance.” — Steve Jobs
Next time you get a really difficult task, sit back, think, and try to break the challenge into smaller parts.
▫ I say yes to temporary solutions.
I tend to use such a trick just to evade a particular task's complete implementation or to meet up deadlines.
Remember: there is no such thing as a temporary code.
Adding code to your application, consider that it can stay there forever.
▫ I assumed code review criteria are good enough.
In the routine everyday development process, it becomes a great challenge to determine how good the code.
Do you support a regular code review or are you limited to the fact that it works as expected?
Ask these questions next time you review a PR.
- Is it easy enough to test the resulting code?
- Can this code be scaled vertically well?
- Is it simple to come up with a name for a certain method or a variable?
- How many methods do you need to redefine?
▫ I assumed complex algorithms always result in a better solution.
How to avoid this:
I have only one piece of advice to give you, which has worked for me ever since I’ve understood how the real world & tech work.
Start simple.
There’s no point in complicating things upfront.
▫ I promote the wrong people.
I assumed a developer is good at their work, they will become good leaders or managers.
Not all good developers are great leaders.
Managing a team is not easy.
It requires proper training to become a coach or mentor.
Whether you are a newcomer in the world of development or you just want to become better.
Times change, technology may become obsolete but your learning should never stop.
The only real mistake is the one from which we learn nothing.
~ John Powell
Thanks for reading. If you like this might be you are interested in my eBook as well.
I have recently written a book for developer growth & shared my 11+ years of experience.
Grab the book now for a weekend offer for just $15 The Prime Guide.
I used to be confused about whether I should introduce myself as a developer, software engineer, front-end engineer, back-end engineer, full-stack engineer, a software engineer in a test, or just a freelancer.
The tech market is the market.
It doesn't care about who you are, as a developer.
-Which degree you hold
-What boot camp you completed
-Which Udemy course you did
It's hard-hitting for some devs initially.
Your emotional & mental state as a dev has a direct impact on your work
And how this will help you to grow as a developer.
A Thread...
To learn any new skill or gain expertise you need to practice, practice, and practice.
There isn’t much debate about that.
But here’s what you might not know:
scientific research shows that the quality of your practice is just as important as the quantity.
And, more interestingly, these scientists also believe that expert-level performance is primarily the result of expert-level practice NOT due to innate talent.
This concept is known as deliberate practice,
and it’s an incredibly powerful tool to grow as a developer.
If you are interested in pursuing a career in development and don't know where to start, here's your go-to guide for salaries, skills, and the best programming languages to learn.
Software development is a dynamic field & getting started the right way as a developer is tough.
-Getting a diploma
-Getting a degree
-Finishing a boot camp
This does not mean the end of studying.
In reality, you are just getting started. While your official studies are over, it does not mean that you do not need to learn new tricks anymore.
HTML elements are the building blocks of the web, and there are tons of different HTML tags out there to choose from, so how do you ensure you're using the right ones?
Let me highlight the tags you should be using to build your sites the correct way.
1. <details> and <summary>
Whenever something on a page needs to be interactive, JS is often the first port of call. Showing & hiding content can be as straightforward as toggling a class.
But this behavior is already available, with no added page weight, right inside HTML.