Profile picture
James Hickey 🇨🇦👨‍💻
@jamesmh_dev
, 4 tweets, 1 min read Read on Twitter
🔥(Senior) Dev Tip: Make devs 100% responsible for their contributions.

Did Fred push code that broke feature X? Rollback and tell Fred to fit it. He will learn to be more careful. He will learn to own his mistakes.

Keep going... 👇
Your team will grow most if they:
- Are given the ability to fail without being "whipped"
- Are given the ability to fail so they can adjust how bold their changes are
- Are noticed and acknowledged when they have success
- Can learn from other's mistakes (😉)

Keep going...👇
What happens if Fred is notorious for breaking stuff? Over and over? His "fixes" almost always break other things? And he still does despite being told to stop?

Well, an environment that encourages responsibility will also allow a lack of responsibility to become apparent.
What do you do in this case? Well, that's another topic for another day (I.e. it's a manager's / HR concern 😋)

Main Takeaway: Giving your team the ability to fail and learn from their failures in a safe environment is the best way to let them grow!
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to James Hickey 🇨🇦👨‍💻
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

More from @jamesmh_dev see all

Profile picture
James Hickey 🇨🇦👨‍💻
@jamesmh_dev
🔥 Dev Tip: I've seen this asked quite a bit on forums etc.

"What programming language should I learn next?"

Nodejs, JavaScript, PHP, MySQL, C#, Python, etc.?

What's my answer?

Thread continued 👇
These are just tools. It's like:
- A guitar to the guitarist
- A pen to the writer
- A hammer to the carpenter
- A car for the racecar driver
A guitarist can know their music theory and "play" well on their own - but that doesn't mean he/she will play well with a group of musicians.

It also doesn't mean they can create beautiful music.
Read 11 tweets
Profile picture
James Hickey 🇨🇦👨‍💻
@jamesmh_dev
Thread for Junior Developers/Engineers:

Bad news - the ability to be a master/elite coder is only the first step in your career 😞

You'll soon find that coding is the easy part.

Some of the hard parts - if you want to progress as a software engineer/developer - are:
1. Being able to communicate clearly in business language - not tech jargon - with business people / non-technical co-workers.
2. A high-level understanding of how systems work:

- design patterns
- how to abstract systems into manageable layers
- how the business or product ought to influence the structure of your app/code
- knowing which technologies solve what high-level problems

etc.
Read 11 tweets

Related threads

Profile picture
Simon Wardley #EEA
@swardley
X : How much does a professional speaker make in a year?
Me : Err ... I guess that depends upon who they are?
X : Can you give me an idea?
Me : No, I'm not a professional speaker. I don't make money from it. I work in research for a company. Ask someone who speaks for a living.
X : I'm trying to work out how much to charge?
Me : Great. I have no idea.
X : But you do lots of speaking.
Me : In 8 years, covering 200+ talks, I will have made from speaking ... let me think .. $0. I work for a company. You need to speak to someone who makes a living speaking.
X : You speak for free?
Me : No, the company charges ... sometimes not if it's more of a community thing. It's a discussion. Speaking takes me away from other things I need to do, so it's a useful constraint and I have to balance things. Making a living from speaking sounds hard.
Read 7 tweets
Profile picture
Tim "Agile Otter" Ottinger
@tottinge
X = fn(1, 34, AFFIRM|REPLY|OTHER, 42.314);

This function prototype is fraught with risk. There are too many things that could go subtly wrong without causing a crash. Worse if you have weak typing (AKA moderately aggressive type coercion).
And yet I see it’s ilk in many programs.
Flags, indicators, meaningful values, digit strings treated as numbers... you can malform the call without warning.

This is why I value small classes.
int celcius = 20;
int fahrenheit = celsius ;

SetTemperature(int x)

Integers are not appropriate here. They make no sense.
The most primitive type isn’t the safest or simplest.
Primitive obsession makes coding complicated and risky.
Read 6 tweets
Profile picture
Simon Wardley #EEA
@swardley
X : What do you think of AGPL?
Me : IMHO, radioactive. Haven't changed my view since 2008 - blog.gardeviance.org/2008/05/data-p…
Personally, I view better licenses are GPL (keeps the SaaS loophole, which is important) or Apache (more commercially friendly).
X : What's wrong with AGPL?
Me : It's a way of poisoning a market in cloud and forcing others to buy a secondary license (i.e. the originator can dual license) in order to compete on operations. Not a fan, don't like it, still don't. The SaaS loophole wasn't a bug but a feature.
X : The AGPL enables ...
Me : Do you map?
X : No
Me : Then you almost certainly don't understand context, competition and why that matters to licenses. This conversation is pointless until you do.
Read 18 tweets
Profile picture
Simon Wardley #EEA
@swardley
X : How to deal with technical debt?
Me : As a rough analogy, I will take liberties, let us start with out Tea Shop example with custom built kettles.
Me : The first thing I do is mark on where things should be ... in this case our operations people are arguing that we should use standard kettles.
I would then add metrics per unit provided (i.e. cup of tea). I will make an awful assumption that the only capital expense is the kettle (i.e. we have depreciation of the kettle) and everything else is variable - paper cups etc.
Read 45 tweets
Profile picture
Steve Smith
@ardalis
When you have two systems that need to communicate, the default for 90+% of companies is to use a shared database. (thread) #dev #programming #architecture #softwarearchitecture
Most never move off of this model, but it has disadvantages that go along with the ease of sharing data. Applications lack encapsulation and cannot adapt their data designs to suit their unique requirements.
Usually the next approach is to treat applications just like components, with exposed public APIs. However, this can result in increased down time since direct API communication between applications means if any is down, the whole thing is down.
Read 7 tweets
Profile picture
Simon Wardley
@swardley
X : Did you invent mapping?
Me : Err, no. That was thousands of years ago.
X : I mean business mapping?
Me : I created my form of mapping now known as Wardley Maps, 13 years ago. It's all creative commons.
X : But what is the first business map?
Me : I don't know of any others.
X : But was it the first?
Me : I doubt it. Never forget Sivowitch's Law of Firsts - "Whenever you prove who was first, the harder you look you will find someone else who was more first"
X : So was it the first or wasn't it?
Me : Who cares? Do you find it useful? Live in today.
X: But what if it wasn't first and someone says this was more first?
Me : I'd be like ... great. Where were you hiding it? Is it a map? Is it a better map?
X : But then you wouldn't be first?
Me : Arghhh. I don't care. Never did. I only care if something is useful.
Read 10 tweets

Trending hashtags

#smartcities #Compliance #aeasf #Transport #facepalm #softwarearchitecture #Code #BeBest #DevRel #ToBeAPartAndNotApart #Accessibility #ai #bigdata #technology #Neurodiversity #opendats #BattleForTheNet #opendara #Fails #opemdata #smartcitiies #Fail #brexit #secdevops #walletconf
Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!

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

Become a Premium Member ($3.00/month or $30.00/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!