Write your answer…

9 answers

"It's never about the code. It's always about the people".

To be honest, I'm still trying to learn this lesson. Most developers get sucked into the code, the language, the framework or the design so much that they actually ignore the people around them. Let me colour this with a few examples. Most developers talk about how productive they are in a particular language or framework. Instead, we should be looking at how productive was it to work with "this" team of developers. In another example, lots of developers even look for jobs that match a language that they know. Instead they should be looking for people they want to work with. The code figures itself out. Bad code is easy to change to good code within a few weeks/days. Bad teams don't become good teams in a few weeks/days. That takes years (if at all).

I'll re-iterate because I think this is important and needs to be said: "It's never about the code. It's always about the people"

2 Beers1
High Five3
Spot On3

And people are so damn hard to debug!

Reply to this…

Hashnode is building a friendly and inclusive dev community. Come jump on the bandwagon!

  • 💬 A beginner friendly place

  • 🧠 Stay in the loop and grow your knowledge

  • 🍕 >500K developers share programming wisdom here

  • ❤️ Support the growing dev community!

Register ( 500k+ developers strong 👊)

The only thing constant is change

Today its technology x, tomorrow it will be y.

First - Learn how to learn

Letting others piss their own bed so they can learn from their failures.

An example of this is recognizing that new and shiny wasn't always better -- and quite often drags you BACK a decade or more as old failures had new names and sick buzzwords slapped on them.

See HTML 5 in terms of JUST being a markup specification, where everything people ooh-ing and aah-ing over have NOTHING to do with HTML -- they're CSS3 and ECMAScript. The only REAL advantages it gives you is a more compact contents for <head>... the new "structural" tags and nonsense like ARIA roles are pointless redundancies to what already existed in 4 Strict (H1..H6, HR, and general semantics), and they undid the attempts at improving accessibility (like letting TARGET into non-frameset documents) and not only created new redundancies (AUDIO, VIDEO are redundant to OBJECT), they greenlit old ones (EMBED). You'd almost think the WhatWG was so ignorant of semantics and the intent of HTML 4 Strict they were unqualified to make HTML 5's successor.

But RECOGNIZING that when everyone is singing praises from the rooftops is a bit of a fight even in your own head.

Same goes for a LOT of the new shiny ECMAScript stuff. A lot of it like some of the new functions are welcome, but you look at the Math object and they added functions for people too lazy to type "1 -" for trig? REALLY? Worse many of the language constructs -- arrow functions, spreads, etc -- just take the already cryptic C syntax and make it even harder to follow.

But RECOGNIZING that when everyone is singing praises from the rooftops is a bit of a fight even in your own head.

Other concepts like "OOP for everything", "functional programming" which is just functions for EVERYTHING no matter how minor, "composition" over "inheritance" all reek of the old joke about how if you have a hammer, everything looks like a nail -- or WORSE just sound like outright gibberish.

But RECOGNIZING that when everyone is singing praises from the rooftops is a bit of a fight even in your own head.

Or how most frameworks actually create more work, less sustainable work, and are in no way, shape, or form any "easier" or "make you more productive". More often than not they violate good practices, are created by people unqualified to tell others how to do things,

But RECOGNIZING that when everyone is singing praises from the rooftops is a bit of a fight even in your own head.

More so when few others see it the way you do blindly parroting those praises no matter how many facts you shove in their face. Ends up feeling like dealing with creationists or cultists.

BUT that's the really hard part, letting others blindly believe their made up fairy tales and basically screw themselves asunder without unloading on them using every four letter word in existence. People NEED to fail so they can learn. The hard lesson is LETTING people fail.

Then knowing how to put up with the fact they are willing to blame everyone and everything EXCEPT the technologies they chose.

Ok, I admit it, I never learned those lessons. But I'm trying.

Discipline .... write/draw it first.

That one is still really hard. Because it feels like wasting time instead of shortening it. Although the result is almost everytime better and faster.

Still most of the time I just want to jump in the code.

Load more responses