Aboutdeveloper of softskill
Joined devRant on 3/26/2020
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Don't be a dumbass and use your 2.4Ghz WiFi and airpods at the same time.
Lessons stux learns at 4am.8
My 4yo monster just randomly told me:
"Mommy! One plus two plus three plus four plus five equals fifteen!"
I'm so proud.
And really surprised 🤔
I've been teaching him basic math (adding and subtracting numbers 0-20), but haven't gone beyond two operations / three numbers.12
Never assume you know better
Never assume others know better
Never assume others know
Trust, but verify [doveriaj, no proveriaj]6
DON'T INTRODUCE NEW FEATURES IN THE WIREFRAME, WHEN WE ALREADY DISCUSSED ALL THE FEATURES IN DETAIL4
After over 20 years as a Software Engineer, Architect, and Manager, I want to pass along some unsolicited advice to junior developers either because I grew through it, or I've had to deal with developers who behaved poorly:
1) Your ego will hurt you FAR more than your junior coding skills. Nobody expects you to be the best early in your career, so don't act like you are.
2) Working independently is a must. It's okay to ask questions, but ask sparingly. Remember, mid and senior level guys need to focus just as much as you do, so before interrupting them, exhaust your resources (Google, Stack Overflow, books, etc..)
3) Working code != good code. You are an author. Write your code so that it can be read. Accept criticism that may seem trivial such as renaming a variable or method. If someone is suggesting it, it's because they didn't know what it did without further investigation.
4) Ask for peer reviews and LISTEN to the critique. Even after 20+ years, I send my code to more junior developers and often get good corrections sent back. (remember the ego thing from tip #1?) Even if they have no critiques for me, sometimes they will see a technique I used and learn from that. Peer reviews are win-win-win.
5) When in doubt, do NOT BS your way out. Refer to someone who knows, or offer to get back to them. Often times, persons other than engineers will take what you said as gospel. If that later turns out to be wrong, a bunch of people will have to get involved to clean up the expectations.
6) Slow down in order to speed up. Always start a task by thinking about the very high level use cases, then slowly work through your logic to achieve that. Rushing to complete, even for senior engineers, usually means less-than-ideal code that somebody will have to maintain.
7) Write documentation, always! Even if your company doesn't take documentation seriously, other engineers will remember how well documented your code is, and they will appreciate you for it/think of you next time that sweet job opens up.
8) Good code is important, but good impressions are better. I have code that is the most embarrassing crap ever still in production to this day. People don't think of me as "that shitty developer who wrote that ugly ass code that one time a decade ago," They think of me as "that developer who was fun to work with and busted his ass." Because of that, I've never been unemployed for more than a day. It's critical to have a good network and good references.
9) Don't shy away from the unknown. It's easy to hope somebody else picks up that task that you don't understand, but you wont learn it if they do. The daunting, unknown tasks are the most rewarding to complete (and trust me, other devs will notice.)
10) Learning is up to you. I can't tell you the number of engineers I passed on hiring because their answer to what they know about PHP7 was: "Nothing. I haven't learned it yet because my current company is still using PHP5." This is YOUR craft. It's not up to your employer to keep you relevant in the job market, it's up to YOU. You don't always need to be a pro at the latest and greatest, but at least read the changelog. Stay abreast of current technology, security threats, etc...
These are just a few quick tips from my experience. Others may chime in with theirs, and some may dispute mine. I wish you all fruitful careers!182
Introducing my everyday weapon against bugs.
Colour pattern to change depending on my mood or my rage against PEBKAC.5
I use my windows computer usually for nothing but games. It's even a shared computer with my wife. But today I have to code something for this computer so I installed IntelliJ on it. And when it was done installing, it asked me to reboot the computer.
Honestly, I feel so nostalgic. Like I am a child again. Thank you IntelliJ or reminding me about my childhood.13
Ubuntu: 100% tests, 367/367 tests succeed
MacOS: 93% tests, 330/367 tests succeed
Windows: 71%, 285/367 tests succeed
Time to boot up a windows vm...
(these numbers are not accurate)5
Designer: can we put the popup at the top of the screen?
Me: You mean op top of the navigation?
Me: I sure can. Would be stupid to block off the site navigation with a popup, but definately possible.
Designer: Cool, let me know when done!
Me: I am done.
Designer: Well now I can't click on the navigation anymore.
Me: That's correct. Let me know when you want to change it again.13
My classmate is a real SAVAGE!!
He (team leader) and his team participated in hackathons several times and kept losing.
He noticed something common about winning team, majority of those team members were women, even if they were non technical and their project was pure bs, they were winning in the name of women empowerment.
This time he came out with a plan, he fired his boys and invited women into his team, and even made one girl the team leader.
Result? HE WON!!!
NOT ONE BUT THREE HACKATHONS BACK TO BACK
His so called women team was invited by Google to pitch their startup idea.
Now, if they gets funding, he's gonna kick out these women and bring back his teammates33
Yesterday I had another job interview. This time from home via Skype. Today I was blown off. I was not technical enough according to the company.
This company was working with an ancient cms nobody ever heard of and made Sass sound difficult and new.
Good luck in the Stone Age fellow devs. Make sure you upgrade your pc to Windows 7.6
Hey devRant. What the fuck is up?
I'm new and just wanted to say hi or whatever. I don't even work in any computer science related job. I'm a fucking welder.
I have aspirations one day to be just like you nerds. I fall asleep at my desk almost every night taking random online programming classes which I lose interest halfway through to some OTHER class and redo the same shit.
Is this what it's like to be smart?42
Some are taking it as a holiday, others still have to meet deadlines while being quarantined.
Source: I am Programmer,I have no life.5
I'm curious - how strict are you (or how strict is your lead / manager) about keeping stuff both detailed and up to date in Jira (both in terms of sprints & tickets)?
I've always drawn a pretty hard line with this - stuff in our Jira environment always has a detailed description, approximate estimate, is kept up-to-date with who's working on it, assigned appropriately, etc. But others I've spoken to seem to barely care if any tasks are in there properly at all.2
Clickbait will never change.
It's the most stable and constant source of mild annoyance.
"These 3 programming languages will net you the highest salary"
"Ten home improvement tips using nothing but recycled underwear"
"How to cut onions like a real chef"
"3 programming languages to learn while being bored in self-quarantine"
"Ten ways to use underwear as facemasks during the pandemic"
"Onions might cure corona, click here to learn how to cut them"
"These 3 programming languages will increase your chances of survival in the wastelands"
"Ten ways to patch up your shelter against radioactive ashes using old underpants"
"Hydroponic onions are a good source of nutrients. Here's how you cut them with your camping knife"16
Working from home is a cool experience for me, but video meetings are a hassle. Not because of the nature of the meeting, but because I need to be sure that certain giant pillow is not visible for the webcam.
Also, for some reason I'm the only one with a stable connection, so there's a large overhead of asking and nobody talking, because we don't know what just happened3
I've just realised, after a couple years of node.js I still don't know how to get command line input.3