Sleep and tackle the problem tomorrow with fresh eyes.
A colleague's eyes are always fresher than your own.
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.
Don't worry, nobody knows what they are doing.
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.
How comes you can only like a comment once?
Some people do, learn from them.
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! :)
Maybe life is too long to be unhappy.
Never stop learning.
Just ask the bloody question!
Haha .. yes! Just ask, already!!!!
Drink less coffee, drink more water
I really want to give up my coffee dependency
Don't be afraid to admit when you're wrong.
Technology is ephemeral; people are not
I have a bad feeling some COBOL code is going to outlive us all.
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
"Get enough sleep" would be my no. 2 advice!
That's why programming is so great. Two paragraphs of explanation condensed in one function! Awesome! Thanks 😄
Any tips on keeping up this discipline?
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.
Ask the question, someone else is probably wondering it too.
Surround yourself with nice people.
You can't be more right! Good one.
Failing is better than not trying.
You've never tested bulletproof vests for a living.
Don't forget to commit
Don't commit directly to master until you're absolutely sure!
Experience is overrated over knowledge, and knowledge over motivation to learn.
Take chances and standout. I wrote about it here:
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.
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.
Don't stop learning, take breaks, learn from mistakes.
Sometimes helps to close your mouth and open your ears.
Work is part of life, so make work worth living.
Keep experimenting. Technically, your way of working and communication.
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.
Know your worth.
Be proactive, curious and finish what you started.
Don't wait to be an expert - put yourself out there.
Protect your eyes. You need them.
"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.
Money isn't everything.
Ask the questions.. share the answers
Connect with people
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."
"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.
Be kind to yourself and others.
Your relationships are everything--cultivate them wisely.
I’m cheating with two separate pieces of short advice.
Results matter, do yourself a favor and focus on them.
If you dislike your job - start looking for a new job.
Learn to speak up. Ask questions when you are stuck.
Reality is negotiable
Check your privilege.
Authenticity + Skill + Diligence + Wisdom + Patience = Career Success
Don't worry if you don't have all the listed requirements
Never stop being curious.
It's not what you say, it's how you say it.
Be humble when someone asks you "obvious" questions.
"Go where you can do the most good."
— A former mentor of mine who had been a manufacturing engineer and art teacher.
Don't overthink, and just build what you like.
Enjoy it, or quit !
from an ex-manager: work hard and don't be an asshole
Be careful what you wish for.
Don’t trust that others know better. Speak up. Ask questions.
Accept that you’ll always be learning. But question things if you never return to those skills and use them.
Believe and keep investing in yourself. Period
Work for a company that does what you do.
Nice take on the format 😊
Keep calm, find ways to be happy with your job.
Participate. Find meaning in your work.
Be honest, work hard, communicate thoughtfully. You should be valued.
Make it work, make it right, make it fast!
Trust your gut
Don't work the weekend because you're worried about deadlines.
Nice person with average knowledge > Bad person with high knowledge
If you found yourself in a rabit hole, stop digging 🤷♂️
Business respects value, not code. Focus on impact.
Play safe. Stay safe. Pay safe.
Buy a safe!
also check out my latest post here:
Don't be too hard on yourself.
Have you tried to restart it?
Study, work eight hours a day, free time.
Don't be afraid of failure!
Every new challenge teaches us something great. Be ready to face any challenge and keep learning from them. This will prepare us to face next bigger challenges.
Technologies come and go. Principles stay.
Knowledge is Life. It increases when you spend it.
Break your problem into small chunks, It will get easier.
Learn what your gut feels like when it’s really excited.
Always be Learning!!!
Find motivations instead of excuses.
If you have the opportunity to challenge yourself, go for it!
(11 words, but it is within the margin of error)
Your word is your reputation and your reputation is your word.
-This is not as trite as it first appears-
Learn from your mistakes. No really... LEARN!
Don't go back to school unless you absolutely must.
Be persistent and never stop learning!
Live life in such way that your name can be googled
If you have a dream, chase it. fail, it's okay, try again, spend your failed quota until finally your dream comes true
Fake it until you make it (within reason)
Learn to learn, avoid big corps if you can ;)
Recursion recursion recursion recursion recursion recursion recursion recursion recursion recursion
Push yourself to beyond your perceived station; accept failure is natural.
When you encounter the genuine article, learn all they teach.
Wow, trying to keep it to only ten words is
Demand, don't ask, to be paid what you're worth.
"Success" is the marriage between competence and opportunity.
If code's work you probably need other hobbies
There's no such thing as over-communication in remote work.
Apply for the job anyway
What's it you do that you're the best in the world at?
Two bits of advice I would give:
Learn something new every day, knowledge is never wasted.
Always surround yourself with people smarter/more knowledgeable than you.
Do what you love, that is what only matters
Be curious, debug all,
keep your inbox empty.
Keep learning, dare, be kind, communicate and report efficiently.
Be always ethical and expect the same from others
Share what you know.
There's a rewarding life outside academia- maybe try software development?
What difference does your position make if you dislike it yourself?
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.