markdown guide
 

Sleep and tackle the problem tomorrow with fresh eyes.

 
 

Too many times has a colleague been able to immediately pin down a problem I'd been pouring HOURS into.

(More junior) teammates often wonder why I'm so verbose with my status-reporting. I can't count the number of times where I've sent out a "I've been banging my head on , here's everything I've done - did I miss something trivial" only to have a reply, a few minutes/hours later, saying something as simple as "line 24 of your problem-description".

 

Doing this one right now. Completely borked the local database for one my apps today. Shut down my machine and went home. Going to play some video games and deal with it in the morning

 

That's why I love doing infrastructure automation: something's gone completely sideways with a system or an entire architecture? Punch a button to deploy a new, functional copy in a few (or few tens of) minutes.

I would love to but we're in feature factory mode so not a ton of time for that level of automation 🙁

Yeah. Automating deployments is definitely a time-suck, but it's a time-suck that, once done, quickly pays for itself by freeing you up to do other thing more quickly and easily. Unfortunately, many organizations that love to say "we want to do devops" or "we want to do infrastructure automation" don't seem to understand that you have to allocate considerable time to getting there. That it's an investment to reach the point where you replace broken systems – or even just do regular patching – with "lemme launch a new copy". Then again, there's a lot of shops that think that re-hosting into a CSP and/or switching to containers magically impart capabilities they never designed into their solutions.

 
 
 

Can confirm. Don’t know what I’m doing.

 

Always amazes me when I run into people that claim to know, with absolute certitude, that what they're doing is the correct, best way to do a given thing.

Usually, such certitude does not bear up under even the most casual of scrutiny.

 
 
 

I know what I'm doing: trying to figure out what I'm supposed to do

 

If you are not happy, do something. Life is short.

 

That’s how I felt after I got my first job my degree trained me for.

I sort of knew how to code and that looked like a lot more fun so I quit and figured out my happy path.

 

+1 Yes, life is too short to be in a crappy job. You can be a team of one but be realistic as well and explore your options. There comes a time when all your pleading and convincing will go to waste if the executives/management don't value your opinion. You deserve to be happy! :)

 
 
 
 
 
 
 

Don’t go to bed if you haven’t learned something new today [repeat every day]

 

Depending on what you consider as "learning something new", you may ruin your sleep really badly :D

 
 
 

That's why programming is so great. Two paragraphs of explanation condensed in one function! Awesome! Thanks 😄

 
 

One and only, IMO: Link this question to an action you do every evening!

For example, washing your teeth, changing clothes, taking a shower, or when pulling the covers on to sleep. Select one action you do religiously every evening, and whenever you do this action, ask yourself the question, "have I learned something new today?". If you can honestly say "yes, I learned something useful today", then sleep sound, you earned it! But if not, then get up and do something, or read something useful on your phone using the DEV app :), etc.

Back when I was around 10 years old, I heard somewhere that the Japanese did this every night. I thought it was SO cool I decided to make that a part of my life. I don't even know if it's true from the Japanese! Also, I thank to my dad, who I saw learning and working really hard every day and night from home, to build his own thing. I learned that, even if all goes south, I can still learn something new every day, and what I learn, I can use to improve my life.

 
 
 
 
 
 

Work hard.
Build relationships.
Find opportunities.
Take chances.
Be kind.

 

Experience is overrated over knowledge, and knowledge over motivation to learn.

 

The best worst advice I can give is "Don't work on other people's dreams, work on your own"

I truly believe in that line, but it's not viable for most people so it's terrible advice.

 

When challenged, try to understand the other person's perspective.

Challenged in this sense doesn't just mean direct conflict, but also when a customer request completely breaks your notions of how the software you wrote is supposed to behave.

 
 

Don't stop learning, take breaks, learn from mistakes.

 

Mistakes are the best thing that can happen to you.

 

I motivate myself through mistakes by thinking about how much I’ll learn by working through the pain and consequences.

 

Work is part of life, so make work worth living.

 

Keep experimenting. Technically, your way of working and communication.

 

Sometimes helps to close your mouth and open your ears.

 

"Find a job where you can get regular wins."

The most soul-crushing part of a job is when you just continually pile frustration upon frustration without ever getting the "high" of achieving a success.

One of the best parts of my prior life as a short-term consultant was that I got that success-high at frequent intervals. It could be as frequent as every couple days but never longer than a month or so. Compare that to long-term consulting... You can go quarters to years with no wins to offset stresses/frustrations. And, yeah, the constant travel sucked (I'd achieved lifetime double-platinum with Marriott after three years of racking up 170+ nights/year with them), but never underestimate how stress relieving regular wins can be.

 

Results matter, do yourself a favor and focus on them.

 

Sometimes you just have to suck it up.

(This is also when you should probably start searching for something new...)

 

You are probably wrong. Review.
They are probably wrong. Review.

 

"He whose life has a why can bear almost any how."
-Friedrich Nietzsche

 

"It's not THAT important, life matters more"

I think/feel like you should care more about you and less about the work

Some people will disagree but I have found that being more focused on me have helped me on being a better developer.

 
 

Your relationships are everything--cultivate them wisely.

 

I’m cheating with two separate pieces of short advice.

  1. Software is for people, not machines
  2. Learn and engage with things other than software.
 
 
 
 
 

Be proactive, curious and finish what you started.

 
 

If you dislike your job - start looking for a new job.

 
 
 

Learn to speak up. Ask questions when you are stuck.

 
  1. Listen first.
  2. You can have it cheap, fast or good. Pick two!
  3. Learn to say "no".
 

Check your privilege.
Be humble.
Keep learning.
Practice self-care.

 

Authenticity + Skill + Diligence + Wisdom + Patience = Career Success

 

Don't worry if you don't have all the listed requirements

 
 
 
 

Be humble when someone asks you "obvious" questions.

 
  1. Most of us are not saving lives
  2. Go on a holiday
  3. Don't just work
Classic DEV Post from Mar 13

Mozilla launches Firefox Send (free encrypted file transfer)

A thread to discuss Firefox Send.

Ben Halpern profile image
A Canadian software developer who thinks he’s funny.

DEV is where software developers grow up

Sign up (for free)