Deni Moka⚡ Profile picture
21 Feb, 11 tweets, 2 min read
It has been 10 years since I wrote my first line of code. Time flies!

Here is a list of 10 honest takes on the job and the industry.

1️⃣ Years of experience is a poor proxy for skill level.

It is not about how many years you spend as a developer.

It is about how much knowledge and experience you fit into those years.
2️⃣ The language-agnostic mindset is way more important than any skill in a specific framework or language.

The tools you learned yesterday can be easily deprecated by tomorrow.

Don't go behind cool frameworks! Go behind solid software engineering disciplines and methodologies.
3️⃣ We are short on good professionals

It's not true that there are not many engineers in the market. There are many of them.

But there is only a few who strives for quality and clean software solutions.

If you want to be differentiated in this market, then strive for quality!
4️⃣ Doing agile is not equal to being agile.

Having daily standups and other mandatory meetings won't make you agile.

Being agile is more about delivering value, being flexible to changes and practicing continuous improvement, rather than following blindly mandatory meetings.
5️⃣ Testability is everything!

Faster and stable releases at lower costs and with more satisfied end-users. That is what every company wants.

We can only reach this by having easily testable software solutions.

Neglecting the importance of testing should be never an option.
6️⃣ The most efficient way to write software is by taking babysteps.

Software engineering is a complex field. There are always many reasons that it can go wrong.

Therefore it's essential to work in short cycles, to get immediate feedback and to continuously verify our software.
7️⃣ There is no such thing silver bullet in this industry.

Software engineering is not black and white. Every problem domain requires different approaches and solutions.

Best practices are not always the best practices.

Pick your stack and apply techniques based on the domain!
8️⃣ Teamwork makes the dreamwork

It does not matter how hard you work, you can not make a big impact alone.

We can only reach incredible results by working in a high functioning software engineering team where it is a pleasure to work in.
9️⃣ Soft skills are equally important to technical skills.

You can be the best software engineer out there, but if you can not communicate and sell your hard skills then you won't be successful.

If you want to get far in this industry, then invest in your soft skills.
🔟 The journey is more important than the goal.

The goal of being a software engineer isn’t to acquire certificates or to finally release a product.

It's about who you become, how many amazing people you meet with, and how much fun and difference you will make on your journey.

• • •

Missing some Tweet in this thread? You can try to force a refresh

Keep Current with Deni Moka⚡

Deni Moka⚡ Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!


Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @dmokafa

18 Jan
Writing good Git commit messages matters!

A thread about how to write clean commit messages:

🧵 👇
1️⃣ Make your commit messages meaningful, explaining the reason for the change. The more explicit the message is, the more helpful it will be.


- fixed
- done
- added 2 class

- add missing validation to login form
- fix bug for calculating cart price
2️⃣ Use the imperative mood

Imperative mood means that the commit message should be written as if giving a command or instruction.


- I have implemented ...
- this commit will ...
- more fixes for broken stuff

- add ...
- fix ...
- remove ...
Read 7 tweets
16 Nov 20
You always wanted to use Test Driven Development (TDD) but you don't know where to start?

Here is a thread for you about TDD in practice.

🧵 👇
1️⃣ Familiarize yourself with the three laws of TDD

These rules are the fundamentals of using TDD in practice. They constrain us to change only one thing at a time. They force us to apply babysteps!

Memorize and strictly follow these rules in order to use TDD efficiently!
2️⃣ Get started with coding Kata exercises

Katas are small programming exercises focusing on small problems.

Solving Kata exercises is a great way to deepen the fundamentals of TDD.

Pick a Kata exercise! You can find many of them here:
Read 7 tweets

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!