SkillsAbap, Java, C, JS,
Joined devRant on 6/9/2018
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Bro : What’s the difference between Git & Github?
Me : Its just like the difference between Porn & Porn Hub. 😎4
The look on a client's face when they realised that I program[med] sex toys for a living was pretty priceless.
Their attitude change, however, cost them a contract. Programming sex toys is no different from programming anything else.
Why do you have to bring in your religious views or my previous contracts into the conversation? All I'm doing is a network audit for your company. I'm not gonna hide a dildo in your closet, or something. I'm supposed to only be around for a few days, too.
Guess I had too many cooties, with how harsh they burnt that contract and bridge.
Those feelings you get when you know @dfox can see you in he's rear view mirror.
-- How I feel at work lately, in terms my wife understands --
Me: There's a gas leak, we need to fix it.
Manager: Yeah, use some duct tape, here's a roll.
Me: That's not how we fix a problem like this.
Manager: Will it work to solve the problem?
Me: Only temporarily
Manager: Ask your co-worker if you need help using duct tape, he's used it before. When will it be fixed?13
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
Dear other developers,
Don't throw exceptions in async callbacks goddammit. It doesn't abort the outer function where you think it does, and it crashes the app because you can't catch it.4
If I have headphones in
and I'm intentionally away from everyone
and it looks like I'm working
and you want to talk to me
Here's some advice:
DON'T FUCKING TALK TO ME.
If you're curious why, I've compiled a list of points:
Also, see Fig. 1 below:
Don't fucking talk to me!28
Fuck today. Today may die in a corner, preferrably in agonizing pain.
Beer, I love you right now ❤11
"Simply log into our portal to access a list of toolkits designed from the ground up to help with your given needs. Using our unique tailored framework we can .... "
Sandra, calm the fuck down. You have a website with some reading material, a form and a few buttons. Get over yourself.2