Member-only story

The Most Important Lessons I’ve Learned From Senior Software Engineers

GreekDataGuy
Better Programming
Published in
5 min readJul 14, 2021
Two women at whiteboard
Photo by ThisIsEngineering from Pexels.

The most crucial software engineering lessons I’ve learned come from two sources:

  1. Failed projects
  2. More experienced developers

Here are some important lessons I’ve learned from senior developers throughout my career.

None are black and white, and there are always exceptions. Only experience can guide you regarding when a rule should be applied or ignored.

Let’s dive in.

Stop Over-Engineering

Nine times out of ten, building more infrastructure, features, or abstraction than necessary is a waste of time.

This is especially true if you work at a startup, where product direction can change with the wind.

While rare cases exist when over-engineering worked out (i.e. WhatsApp), it’s not a good idea for most companies.

I know this firsthand. Having spent most of my career in startups, I’ve written tons of code that never made it to market or gained traction at all.

Over-engineering has two causes

  1. Inexperienced PMs who won’t cut…

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

GreekDataGuy
GreekDataGuy

Written by GreekDataGuy

Just a developer. Contact: greek.data.guy “at” gmail.com

Write a response