!rant

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!

Making a popping sound with my mouth when I do an array.pop() or git stash pop. Every damn time.

What the flying fuck is happening on the EU with the fucking GDPR corsairs!!

I made two - TWO - entirely static websites, hand-made, 100% cookie-free!! I didn't even need to store a goddam boolean cookie! No third-party content is EVER invoked, called or summoned! I hosted a small video to avoid Youtube! Facebook and twitter share buttons are links!! I DID ALL OF THIS ON PURPOSE AND INFORMED THE FUCKING CLIENT.

And THEN (and, of course, unsolicited), the fucking lawyers of an asshole GDPR corsair office came and scared the shit out of my clients and convinced BOTH of them to put the goddam GDPR cookie consent popup on the fucking websites!! And they took their bribe, of course...

In order to avoid billionaire fines because of the NON EXISTENT cookies of the SMALLEST, SIMPLEST, 2KB MINIFIED HTML page on the Internet.

Anybody else is suffering from this kind of behavior??

I used PHPMailer to send emails to a client's website user. SMTP host is smtp.gmail.com.

web was hosted on Bluehost. I found out that mailer was not working. I enabled verbose output and to my surprise I found out that Bluehost was intercepting my mail and responding with

220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail

when i was explicitly using smtp.gmail.com. Not only they were intercepting but also They were trying my credentials against its own smtp server and then showing me that authentication failed.

When i contacted chat they asked me to tell last 4 characters of Bluehost account password to verify ownership.

Dude do they have passwords in plaintext.🤔

Online tutorial pet peeves
————————————

My top 10 points of unsolicited ranting/advice to those making video tutorials:

1. Avoid lots of pauses, saying “umm” too much, or other unnecessary redundancy in speech (listen to yourself in a recording)

2. If I can’t understand you at 1.5 - 2x playback speed and you don’t already speak relatively quickly and clearly, I’m probably not going to watch for long (mumbling, inconsistent microphone volume, and background noise/music are frequent culprits)

3. It’s ok to make mistakes in a tutorial, so long as you also fix them in the tutorial (e.g., the code that is missing a semicolon that all of a sudden has one after it compiles correctly — but no mention of fixing it or the compiler error that would have been received the first time). With that said, it’s fine to fix mistakes pertinent to the topic being taught, but don’t make me watch you troubleshoot your non-relevant computer issues or problems created by your specific preferences (e.g., IDE functionality not working as expected when no specific IDE was prescribed for the tutorial)

4. Don’t make me wait on your slow computer to do something in silence—either teach me something while it’s working or edit the video to remove the lull

5. You knew you were recording your screen. Close your email, chat, and other applications that create notifications before recording. Or at least please don’t check them and respond while recording and not edit it out of the video

6. Stay on topic. I’m watching your video to learn about something specific. A little personality is good, but excessive tangents are often a waste of my time

7. [Specific to YouTube] Don’t block my view of important content with annotations (and ads, if within your control)

8. If you aren’t uploading quality HD recordings, enlarge your font! Don’t make me have to guess what character you typed

9. Have a game plan (i.e., objectives) before hitting the record button

10. Remember that it’s easier to rant and complain than to do something constructive. Thank you for spending your time making tutorial videos. It’s better for you to make videos and commit all my pet peeves listed above than to not make videos at all—don’t let one guy’s rant stop you from sharing your knowledge and experience (but if it helps you, you’re welcome—and you just might gain a new viewer!)

Well now, I wouldn't want to mention anyone specific since talking about someone behind their back and calling them 'weird' isn't very nice. 🙄 But absolutely HYPOTHETICALLY speaking, if I HAD a weird coworker, they would probably...
- ... strut about the office, telling all how great yet underpaid their work is
- ... write lots of 'concepts' because coding is for lowly programmers
- ... insist that the code they have to do when boss is looking is simply too complicated for unit testing, and 'that's great!'
- ... brag about their/wear to work a ridiculous array of ties in every colour imaginable, when everyone else shows up casual

- ... trap people into listening to them talk for hours about...
-- ... ties
-- ... their misspent youth
-- ... how awesome they are/were/will be
-- ... why it's a good idea to eat cheese

- ... never let me forget I'm female, coz *insert BS reasons why all devs must by nature be male here*
- ... send me little unsolicited notes and mails with funny (sexist) jokes *har har*

- ... be let go, at which point everyone else discovers why they had so much time that they could spend chatting away at the watering hole
- ... earn the eternal hatred of anyone picking up the pieces of their 'work'
- ... try to steal our customers away who will laugh in their bloody face

Just my theory, of course..

When you walk away from your Windows 10 box for a meeting and come back in the middle of an unsolicited reboot. Where's my axe?

I hate it when my manager lurks around when i am debugging and keeps giving random unsolicited advices. I spend more time explaining him why what he is saying does not make any sense than debugging.

Stop asking for a ++. The whole point of that is to give it unsolicited, otherwise it devalues what ++ means for everyone else. I earn my ++'s.

And no I don't have change for coffee!

As a pretty solid Angular dev getting thrown a react project over the fence by his PM I can say:

FUCK REACT!

It is nigh impossible to write well structured, readable, well modularized code with it and not twist your mind in recursion from "lift state up" and "rendercycle downwards only"

Try writing a modular modal as a modern function component with interchangeable children (passeable to the component as it should be) that uses portals and returns the result of the passed children components.

Closest I found to it is:
c o d e s a n d b o x.io/s/7w6mq72l2q
(and its a fucking nightmare logic wise and readability wise)

And also I still wouldn't know right of the bat how to get the result from the passed child components with all the oneway binding CLUSTERFUCK.

And even if you manage to there is no chance to do it async as it should be.
You HAVE to write a lot of "HTML" tags in the DOM that practically should not be anywhere but in async functions.

In Angular this is a breeze and works like a charm.
Its not even much gray matter to it...

I can´t comprehend how companies decide to write real big web apps with it.

They must be a MESS to maintain.

For a small "four components that show a counter and fetch user images" - OK.
But fo a big webapp with a big team etc. etc.?

Asking stuff about it on Stackoverflow I got edited unsolicited as fuck and downvoted as fuck in an instant.
Nobody explained anything or even cared to look at my Stackblitz.
Unsolicited edit, downvote, closevote and of they go - no help provided whatsoever.
Its completely fine if you don't have time to help strangers - but then at least do not stomp on beginners like that.
I immediately regretted asking a toxic community like this something that I genuinely seem to not understand. Wasn't SO about helping people?
I deleted my post there and won't be coming back and doing something productive there anytime soon.

Out of respect for my clients budget I'm now doing it the ugly react way and forget about my software architecture standards but as soon as I can I will advise switching to Angular.

If you made it here: WOW
Thank you for giving me a vent to let off some steam :)

In a forum far far away...
<user> I need help understanding something about this library.
<various users> This is how it works. This is something to consider. Here is a good way to learn all of this. etc Really helpful people.
<user> I would say more about what I want to do, but I don't want to receive any more "mouthful of unsolicited advises ".

Really? You fucking ask a question on a forum about what you want to learn. Everyone there takes it seriously and provides some really golden shit on how to learn the topic. Then you shit on them for daring to provide ways to learn the topic?

I don't know if this is a language barrier, or if they are using Google translate. I have no idea. But they come across as an asshole.

How am I supposed to deal with unwanted swag? I attended a VR dev meetup (turned out to be pure corporate advertising) and someone placed unsolicited swag at my desk. After the corporate spiel I privately asked one of the coordinators where to return this because I don't want to put it to waste. He called me rude and walked away.

A day can hardly pass now before I get numerous unsolicited messages on LinkedIn from recruiters that want to know if I'm miserable at my current job and want to jump ship.

It used to be very fascinating back in the days but kinda annoying these days. My inbox is now full of such messages and it's beginning to get to me. I even got one a few days after I started a new job. Like what the actual fuck. My profile clearly says I recently moved to a new company.

I also have numerous pending friend requests from a lot of recuiters like i want my network to be filled with only recuiters. That's not why i joined LinkedIn and have an up to date profile.

I just want to be left alone and not be bothered and mentally harassed by recuiters on LinkedIn. Is that too much to ask???

The presumption of incompetence:

Has this ever happened to you?

Starting a task and chatting with a fellow dev-- my first time implementing analytics in this particular app. I mentioned to them that I've been doing analytics implementation on various apps at our company for years, but our current apps' analytics setup is the most intense and this will be a good learning experience for me to dig into.

They responded by sending me code snippets of existing analytics implementations to help me. Not hidden or lesser-known classes, very obvious ones I already had open and was working off of. With advice like "just search the codebase for 'analytics' and 'trackPage''" lol.

I like this person a lot, but this definitely caught me off guard. It felt like something her obtuse manager would do, but not her. This would probably not be a big deal to most but I'm so used to being given unsolicited/unhelpful/irrelevant advice from male devs, and having to be pleasant and thank them, this one was tough to witness.

How do you respond to unsolicited "help"? Does it bruise your ego the way it bruises mine? lol

A local employer is getting desperate in my area I think. My wife owns a business and talks to people from all sorts of backgrounds. Today a hiring manager that employs software engineers talked to my wife. My wife mentioned that I write software. They now want to talk to me. I have seen their adverts and thought about applying. Pretty sure they will pay a lot more than my current employer.

I think the universe might be telling me something.

Somewhere in the svalbard vault where github buried all our code is about two hundred megabytes of pictures of my ass and other pornography stenographically hidden in innocous pictures hosted on github. Why? Because I can.

I did the same thing with stock photography back when I used to be a photographer. If you've used pixabay or a dozen other stock sites theres a good chance you've unwittingly looked at my magnificently sculpted ass (and other parts of me).

Future shenanigans include massive (and unsolicited) deliveries of half finished dildos (courtesy of dildo factory dumpster rejects), public accesible blue tooth speakers put in inaccesible spots, deepfakes of opposing politicians banging uglies, public book burnings not because we hate books but because who the fuck reads anymore?

And orgies, lots of orgies.

Its the end of the world. Let loose with the craziness and party.

No matter how much I try my boss keeps trying to shove future or unsolicited features on every fucking current sprint as if we weren't delayed already...

Wtf dude? We get paid by delivery, let's just fucking deliver what they expect by each deadline and move on...

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.
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.
Working independently is a must. It's okay to ask questions, but ask sparingly.
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.
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!

Today, I got my first recruiter spam (read: unsolicited) email! If they get more common than that, I'll have to build a filter for those.

I hate that services think that just because you sign up for their service (even just to use once - such as a job board or something) they have permission to send you unlimited, unsolicited marketing emails.

If I found the original creator of such a practice, I would waterboard them with vodka.

Thank you, Slack

Learn More is just a bunch of unsolicited instructions

I hate to offer some unsolicited critique of something I happily use for free... but I have to say this somewhere to just get it out. That's what this place is for, right?

The new MDN visual design fucking sucks.

It's like a purposeful example I might make for my students - of "what not to do." There were a few things they could have done to improve MDN for sure. Instead, they didn't improve it. They just "changed it." That is always a bad move. Now everything just has less contrast and is floating around with nothing to anchor it. Didn't they show it to anyone and get feedback along the way? "So, we made all the fonts closer to the same size, removed any differentiation in weight so that everything will look the same and just kinda blur out and put people to sleep, and just in general dulled everything out as much as possible - and also here's this logo thing too."

You give out your e-mail address at a conference and they start abusing it for all sorts of marketing purposes..

Fuckers.

Any of us had annoyances with people with “a million dollar app idea” but what about these which gives unsolicited career advice?

I’m dealing with a boomer which keeps trying me to change my career and work into cyber security (because TV told him it’s a well paid field) despite me kindly telling him for multiple times which it’s not going to happen because I won’t throw away a career I love to work in a field which seems deadly boring to me (I love anything about coding from design to typing for hours on Vim meanwhile the only thought of reading for hours obscure documentation to find potential vulnerabilities on a system kills my spirit).

Being a "tech guru" person of the family, do you ever get unsolicited pics of gadgets?

Me: I am your fucking senior engineer...!
Co-founder: well, I still think there's nothing wrong with creating unsolicited user accounts and sending them mails unless you can quote a word-class source

"Unsolicited redesigns are terrific and fun and useful, and I hope designers never stop doing them. But as they do so, I also hope they remember it helps no one – least of all the author of the redesign – to assume the worst about the original source and the people who work hard to maintain and improve it, even though those efforts may seem imperfect from the outside." - Khoi Vinh

A moodlecloud subdomain is sending me unsolicited emails, I have no way of contacting them, and the moodle support team is just stonewalling me.

The lack of ownership in society really sucks sometimes

Maybe not specifically "dev" but certainly a relatable rant to anyone here:
Moms small business gets "hacked," or standard spyware phone call from India let us save you for only $149 kind of crap. She obviously gets upset had a panic attack and thinks about all the sensitive shit on their network. Then, ONLY THEN, does she call me and the rest of the cavalry i.e. over payed and undermotivated IT guy to ask what's up why it happened and whose fault is it.

All is well, no ransom paid, no data lost or tangible damage done, but I am positive it will happen again, because it is impossible for people to internalize that they're the problem that money can't fix.

You clicked the unsolicited link. No amount of antivirus bloatware will ever be able to stop the monkey from trying to see what's in the box.

TheBut keep not paying me or people more qualified than me, and then scream and yell and pout when your shits gone and we can honestly say with a grin and a clean conscience that there is nothing we can do.

I shake my head at companies who think sending me unsolicited emails/texts is going to encourage me to do business with them. :P

When a recruiter makes an unsolicited call. Becomes all chummy and then when you tell them that you’re not looking, they have the cheek to ask you for references for *insert common buzzword here* and expect me to divulge information about contacts.