!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!

Pro tip: If you are a junior, or senior but new at the company, don't start your conversations with:

"We're doing X wrong. At my previous company we did / at school I learned /in this book I read / according to this talk I watched, the right way to do X is ..."

Instead try:

"I'm curious why were doing X this way. I'm used to doing it differently."

I love flat-hierarchy teams, and people who think about flaws in procedures and proactively try to improve the tools we use are awesome, but the next kid walking up to me yelling we use git flow "wrong" will be smacked in the face with a keyboard.

If you come to me with curiosity and an open mind, I'll explain, and even return the favor by behaving the same way when I'm baffled by your seemingly retarded implementations.

Maybe we can learn from each other, maybe discover that "how I learned it" is sometimes good, sometimes bad.

But let's start with some social skills, not kicking off into every debate with a stretched leg and a red face.

Pro tip - Infect your computer with small viruses to build its immune system.
Kinda shitty tip

"sudo !!" Will rerun your last command with sudo privileges in a Linux environment.

You're welcome.

Pro Tip: You can drastically reduce keystrokes in any editor by using your brain before typing.

Pro tip:
Decorate your room like a lecture hall so you fall asleep faster

Pro tip: code in binary so it takes less time to compile

Me: double-taps rant to like it
DevRant: "Pro tip: You can double-tap rants to like them"

Pro tip to error messages #1: keep them simple and short

Pro tip to error messages #2: make them make FUCKING SENSE

Happy Holidays!

Pro tip:

Although 'hmm either kill it or if that doesn't work, sacrifice some of its children' is a perfectly valid sentence in the sysadmin world, it's not in public.

😅

Pro Tip: Act like you know what you're doing even if you have no idea.

Pro tip: NEVER work when you’re tired, and if you absolutely HAVE to, make sure you do it in your TIRED branch.

Pro tip: preserve your job by not documenting it.

Pro Tip: You can also charge your laptop faster by placing it carefully in the microwave and setting the timer for 10 minutes.

If all else fails; jumping off a bridge is also another natural way of preventing you from getting your devices infected

Pro tip: if you encrypt your message with ROT13 twice, the security is also doubled

Pro tip: when taking a picture of your computer screen, make sure to turn the flash on

*burp* Me..Merry Christmas

I made a thing. It's called Claymore.

It's like lastPass, but with a bomb attached to it.

Its *burp* like, if you're like really paranoid about your passwords, you can just, you can just blow it all up.

Pro-Tip, if you run it on port 1337, it's extra sec-*burp*-ure.

Am I kidding? Maybe. I made this w/ booze, so.

Actual pro tip: don't push only when you are done with code. Always push when you are done with coding session. Minimize the possibility of data loss and always have your code on the server.

Pro tip: It is faster and easier to say 'World Wide Web' than it is to say 'WWW'.
You're Welcome!

Pro tip for all you who struggle to complete your side projects:

Pro tip: As great as your product is, it's 1000x harder to pitch to my boss when it has a goofy-ass name.

Me: Hey boss, I came across some new software that'll help manage our mission critical database system.
Boss: Oh yeah, what's it called?
Me: WoolySocksDB Enterprise Edition
Boss: 😐... No.

Pro-Tip: Debugging/Logging with emojis is so much more fun

Pro tip when working on colleague's dirty computer! Even touchpad works!

Pro tip: if you want to day dream at work just open a complicated XML file in your IDE and stare at it intensely any time someone walks past your desk.

Long rant ahead.. so feel free to refill your cup of coffee and have a seat 🙂

It's completely useless. At least in the school I went to, the teachers were worse than useless. It's a bit of an old story that I've told quite a few times already, but I had a dispute with said teachers at some point after which I wasn't able nor willing to fully do the classes anymore.

So, just to set the stage.. le me, die-hard Linux user, and reasonably initiated in networking and security already, to the point that I really only needed half an ear to follow along with the classes, while most of the time I was just working on my own servers to pass the time instead. I noticed that the Moodle website that the school was using to do a big chunk of the course material with, wasn't TLS-secured. So whenever the class begins and everyone logs in to the Moodle website..? Yeah.. it wouldn't be hard for anyone in that class to steal everyone else's credentials, including the teacher's (as they were using the same network).

So I brought it up a few times in the first year, teacher was like "yeah yeah we'll do it at some point". Shortly before summer break I took the security teacher aside after class and mentioned it another time - please please take the opportunity to do it during summer break.

Coming back in September.. nothing happened. Maybe I needed to bring in more evidence that this is a serious issue, so I asked the security teacher: can I make a proper PoC using my machines in my home network to steal the credentials of my own Moodle account and mail a screencast to you as a private disclosure? She said "yeah sure, that's fine".
Pro tip: make the people involved sign a written contract for this!!! It'll cover your ass when they decide to be dicks.. which spoiler alert, these teachers decided they wanted to be.

So I made the PoC, mailed it to them, yada yada yada... Soon after, next class, and I noticed that my VPN server was blocked. Now I used my personal VPN server at the time mostly to access a file server at home to securely fetch documents I needed in class, without having to carry an external hard drive with me all the time. However it was also used for gateway redirection (i.e. the main purpose of commercial VPN's, le new IP for "le onenumity"). I mean for example, if some douche in that class would've decided to ARP poison the network and steal credentials, my VPN connection would've prevented that.. it was a decent workaround. But now it's for some reason causing Moodle to throw some type of 403.

Asked the teacher for routers and switches I had a class from at the time.. why is my VPN server blocked? He replied with the statement that "yeah we blocked it because you can bypass the firewall with that and watch porn in class".
Alright, fair enough. I can indeed bypass the firewall with that. But watch porn.. in class? I mean I'm a bit of an exhibitionist too, but in a fucking class!? And why right after that PoC, while I've been using that VPN connection for over a year?

Not too long after that, I prematurely left that class out of sheer frustration (I remember browsing devRant with the intent to write about it while the teacher was watching 😂), and left while looking that teacher dead in the eyes.. and never have I been that cold to someone while calling them a fucking idiot.

Shortly after I've also received an email from them in which they stated that they wanted compensation for "the disruption of good service". They actually thought that I had hacked into their servers. Security teachers, ostensibly technical people, if I may add. Never seen anyone more incompetent than those 3 motherfuckers that plotted against me to save their own asses for making such a shitty infrastructure. Regarding that mail, I not so friendly replied to them that they could settle it in court if they wanted to.. but that I already knew who would win that case. Haven't heard of them since.

So yeah. That's why I regard those expensive shitty pieces of paper as such. The only thing they prove is that someone somewhere with some unknown degree of competence confirms that you know something. I think there's far too many unknowns in there.

Nowadays I'm putting my bets on a certification from the Linux Professional Institute - a renowned and well-regarded certification body in sysadmin. Last February at FOSDEM I did half of the LPIC-1 certification exam, next year I'll do the other half. With the amount of reputation the LPI has behind it, I believe that's a far better route to go with than some random school somewhere.

Pro-tip #526:
Do NOT short your power supply.

Pro tip: never start a client project for free...

Pro tip: never set custom script stuff related to dns server forcing things in a root firewall app if you don't know what you're doing.

How would I know? There's a slight chance that I just went offline for a few days (mobile only) to figure this shit out 😅

All fixed now, though!

Pro tip: never try to convert the date (formatted as "yyMMddHHmm") in an int32.
It will stop working in 2022. 😉

I just found out I accidentally invented the "2022 bug" two years ago.

Pro Tip: if you're building a developer REST API, don't forget to add a sample response to each endpoint. I don't want to have to test each one when I'm building my integration, I'd rather build my model in one go with the documentation displayed on a second monitor.

Pro tip of the decade found on quora:
How to beat procrastination?
Start by this :" I will start my work in 5...4...3...2...1" and just jump of the place and go to work

Pro security tip:
Use a very simple password because h4x0rs expect a difficult one so they can't cr4ck yours

Pro tip to scrum masters: bringing a scrum suitcase to your sprint meetings is more useful than bringing scrumbags.

Pro tip for job candidates:
If you push a code challenge to a live hosting service like github pages or S3, don’t give the reviewers a link to the repo!! Instead put the link into the home page and send the reviewer only a link to the live hosted page.

Why?

Because, if you host with github pages, you’re required to use the project path as the domain root. If the reviewer pulls your project and doesn’t bother to read your readme file with the link at the top, he’ll complain that he couldn’t figure out why your project isn’t hosted from the root domain, and he’ll pass on your application.

True story.

Pro tip:

Make sure you can RECOVER from your backups.

It's all well and good backing this and that up, but make sure that when the shit really hits the fan you can recover.

I've now 4 days into recovering a raspberry pi that ran:
Pi-hole
Snort
DHCP
VSFTP
Logwatch
Splunk forwarder
Grafana

And serveral other things... I've learnt my lesson

Pro-tip to self: Getting syntax errors on your If-Than statements? Try using If-Then instead!

*facepalms at own stupidity*

Pro devRant tip:

Search for "client". Those are some of the best rants.

Coder life pro tip : do not open terminal in public. As people may think you are a terrorist trying to hack the airport. 👍

This is the craziest shit... MY FUCKING SERVER JUST SET ON FIRE!!!

Like seriously its hot news (can't resist the puns), it's actually really bad news and I'm just in shock (it's not everyday you find out your running the hottest stack in the country :-P)... I thought it slow as fuck this morning but the office internet was also on the fritz so I carried on with my life until EVERYTHING went down (completely down - poof gone) and within 2 minutes I had a technician from the data centre telling me that something to do with fans had failed and they caught fire, melted and have become one with the hardware. WTF? The last time I went to the data centre it was so cold I pissed sitting down for 2 days because my dick vanished.

I'm just so fucking torn right now because initially I was absolutely fucking ecstatic - 1 week ago after a year of doomsday bitching about having a single point of failure and me not being a sysadmin only to have them look at me like I'm some kind of techie flat earther I finally got approval to spend around 5x more per month and migrate all our software to containerized micro services.

I'll admit this is a bit worse than I expected but thanks to last week at least I have recent off site images of the drives - because big surprise I have to set this monolithic beast back up (No small feat - its gonna be a long night) on a fresh VPS, I also have to do it on premises or the data will only finish uploading sometime next week.

Pro Tip: If your also pleading for more resources/better production environment only to be stone walled the second you mention there's a cost attached be like me - I gave them an ultimatum, either I deploy the software on a stack that's manageable or they man the fuck up and pay a sys admin (This idea got them really amped up until they checked how much decent sys admins cost).

Now I have very flexible pockets because even if I go rambo the max server costs would only be 15-20% of a sys admins paycheck even though that is 13 x more than our current costs.

Pro tip: Don't cheap out on dongles for newer macbook models.. Bought a (somewhat) working Chinese dongle with 4 ports. Fire hazard and I think my 13" mbp just farted a fireball

Pro Tip: If you spent all day debugging and shit's still not working, go get yourself an oversized, fully functional enter-key-pillow. Your code will probably still not work, but now you can at least spare your keyboard and smash that enter-key with all your built up rage

Discovered pro tip of my life :
Never trust your code

Achievements unlocked :
Successfully running C++ GPU accelerated offscreen rendering engine with texture loading code having faulty validation bug over a year on production for more than 1.5M daily Android active users without any issues.

History : Recently I was writing a new rendering engineering that uses our GPU pipeline engine.. and our prototype android app benchmark test always fails with black rendering frame detection assertion.

Practice:
Spend more than a month to debug a GPU pipeline system based on directed acyclic graph based rendering algorithm.

New abilities added :
Able to debug OpenGL ES code on Android using print statement placed in source code using binary search.

But why?
I was aware of the issue over a month and just ignored it thinking it's a driver bug in my android device.. but when the api was used by one of Android dev, he reported the same issue. In the same day at night 2:59AM ....

Satan came to me and told me that " ok listen man, here is what I am gonna do with you today, your new code will be going production in a week, and the renderer will give you just one black frame after random time, and after today 3AM, your code will not show GL Errors if you debug or trace. Buhahahaha ahhaha haahha..... Puffff"

And he was gone..
Thanks satan for not killing me.. I will not trust stable production code anymore enevn though every line is documented and peer reviewed.

Pro Tip: If you're working Tier 1 tech support, before you start reading your script to the caller, be sure to let the caller complete at least one sentence to tell you what steps he's performed and what the error message is vs. what you're thinking it is. That'll save you from a lot of grief with your boss who will ask you why the customer was screaming at you on the call recording to SHUT UP FOR A SECOND SO I CAN FINISH TELLING YOU WHAT THE PROBLEM IS!!!!!!!!!!!!!

Pro tip. How to cut down on those pesky support emails? Break the only email link in your app I can find.

Genius.

*Pro tip:* add comments in your code stating what you're gonna write next! This helps the reader to know what to expect!

[filename EventsTable.js]

Rant time of 'Derp & Co.'

Today I decided that I am going to find another job, I just can't keep with this shit.

They said that use Agile: FALSE.
• Daily (best scenario) take like 1 hour and a half.
• New task enter the sprint and "Fuck you, more task in the same time". This is something regular done.

• "Oh, dev, we need you to check this other project" I am in the middle of my sprint on this project. "But you have to fix this bug here". (3 fucking days the bloody bug) "You are late again with tasks".

• Meeting for fresh sprint: 6 BLOODY hours... nonstop

The workflow is garbage:
• SOMEONE should did all the devops shit on the first sprint, guess what? They did nothing!, guess now who is being blamed for it (not only me, but a few coworkers).

• Nothing is well designed/defined:
~ task are explained like shit
~ times measured wrongly
~ We are in the last fucking SPRINT and still doing de ER of the DataBase cause Oh, apparently no one has work before with SQL (damn you MongoDB! (Not really)) so I am doing my best, but "jezz dev, this is so hard... maybe we can do it WRONG and easy".
~ No one is capable of take responsability of their mess, they just try to push down the problems. (Remember the devops situatuion? Why is.my fault? I came at the 3 or 4 sprint and I am doing backend tasks, I know nothing about devops).

But the big prize, the last one:
• Apparently you can't send whatever you want to the boss, it has to pass a filter previously of coordinators and managers, hell yeah!

And I am an idiot too!
because I see that we can't reach our schedule and do hours on my spare time!
This is because there are a few good coworkers who probably ended with my unfinished tasks... and they are equaly fucked as me...

This is just the tip of the iceberg. I am not a pro, I am not a full stack developer and still need to learn a lot, but this is just not normal, eight months like this...

Pro Tip: Add a technology that you want to learn to your resume and send it in order to stop procrastinating learning it

!rant

Pro tip: if you wear a full face mask with a BiPap, do not start puking in your sleep.

Glad my body apparently decided to nope the hell out as soon as I started aspirating, but it was still a singularly unpleasant experience I hope never to repeat.

Thankful to still be alive.

Pro tip: how to reply to more than one person
1) click reply
2) close the reply by pressing the x button in the upper left hand corner.
3) click reply button of another person. Their name should now be added
4) Reference a Null Pointer
5) Profit?

I just found out you can commit single lines of a file without the necessity to remove temporarily debug lines every time ... it has blown my mind.

Pro Tip #12:

If you boot of HDD buy one of the cheap 240 GB SSD and try yourself. Windows finally boots in less than 5000 min.

One Pro Tip for all developers :

(in my experience - a short story)

Our team chose agile development. We have items to deliver each sprint.

I was the guy who would always slip in my tasks due to issues that would pop up.
It was due to my own faults, I was less careful and failed to concentrate on one single item when I was working.
I started slipping a lot and my manager started questioning me on my performance. I tried a lot of productivity apps and other methods. Nothing seemed to change my life.

One day, An experienced person in the team said to me,
"Start Going to the gym" and it'll change everything.

I enrolled to the nearest gym and started working out every morning. Had sore arms /legs in the first few days. Nothing seemed to change.

After one week, my work patterns changed. I automatically started to work with a lot of concentration. I still don't know how things changed.
After 2 weeks, everything was completely different.

I was able to complete my sprint tasks in the first few days and started contributing to others work. Got a lot of recognition. My work was recognized a lot and my manager appreciated me.

So this is a real life changer folks.

"start hitting the GYM", and it'll change your life.

Please try it out and tell me how your work patterns change.

I need to setup a Windows Server with an AD (and therefore an own domain) that can be reached from a Linux host for a test environment... Holy crap I totally forgot what a huge pain in the ass that crap is!

Pro Tip: If youre connected to a Server via VPN and RDP and you create a domain and subsequently get logged out from the server, you're fucked.

Pro tip: using enums you can make a type that can be one of two values. Perfect for control structures! #codelikeapro

Sunday guilt: Do I ssh in and finish the testing I didnt mange Friday? Pro-Tip: never set up your work VPN.

Pro tip: when recompiling code there are no miracles. If garbage goes in, garbage comes out.

Pro tip: always make sure your methods return the correct variable.

I’m currently working with deep neural networks using tensorflow. I needed to generate some test data and wrote a program to create it. I had two text files which each consisted of approximately 5000 lines of text.

I wrote a method that should sort out some words, and make my final data shorter. When I executed the program first time on our server, it spent about 25 minutes, then crashed due to MemoryError (which in Python means that the server didn’t have enough ram). That seemed quite weird since I only had about 10k lines of text, and I even sorted out a bunch of it, and the server has 128gb ram, and nothing’s using it.

Apparently I returned the wrong variable. That meant that my program tried to save 750 quadrillion lines of text rather than just a few thousand.

Always make sure to return the correct variables!

Python async is a total, unapologetic shitshow. It’s as if the design goal was explicitly to invalidate the maximum number of thoughtful stackoverflow QAs possible. Pro tip: make you sure to memorize the release dates of every minor version of python from 3.5-3.10, so that you know which stackoverflow answers are not relevant in any way to your codebase.

Pro tip: if you press the little refresh button on the upper right hand corner it will refresh the rant and then scroll you all the way down to the bottom of the page.

Android studio's pro tip:

1)While installing it for the first time, just edit idea.properties(open it in notepad,its a text file with instructions already there) and change the system and caches directory to your custom defined directory with space > 8gb before installing
(Yeah that's the amount of cache generated when you have 5 projects open in parallel and when its being created in your root folder, your system hangs{personal observations, can't assure})

2) similarly click on "set custom location" and don't go with the "set recommended location" when asked where to install android studio's sdk.

Pro tip: get more battery life with one simple hack: remove the battery 🔋

pro tip: If the scroll wheel is not working on your mouse in #Linux, ensure the user is in the wheel group. 🤓

Job interview pro-tip: when it's your turn to ask the questions, the first one you ask is "Is this job in an open-plan office?" If the answer is 'yes,' say 'thank you,' get up, and run out of there like your productivity depended on it.

DevRant Pro Tip: Use emojis in your tags

Pro-Tip: If you change your `div` to `li` and then decide to change them to `span`, check before you replace all lest you end up with `Navspannk` from ‘react-router-dom’. Why are my styles not working? Ah, they are ‘spannkStyles’ now.

Pro TIP :

If you have a lot of work and SOMEONE from your team is disturbing you every hour,
Move away (alone) to a meeting room, away from your stupid teammates for one day. For High productivity work.

Pro tip: Never test old HDDs with one of those Samsung USB3 to SATA adapters. Always use a test bench with real connectors. It might save you a few believed to be dead HDDs.

Hey guys! So I just woke up from a dream in which I was talking with skilled programmer and he gave me awesome pro tip which I'd never realize exists!

But it was my dream so my idea. I have no idea how the f*ck this works but it's awesome. Is it just me or ?

Just spent 30+ hrs on an error that was due to using flatMap instead of map.

I feel stupid!

Pro Tip: Never try to learn Spring without learning java properly.

Pro tip: don’t accept a meeting with a potential employer for the beginning of your holidays (I know, ’muricans, you don’t get this concept where basically everyone taked paid vacation for several weeks during summer) so that you’ll end up thinking about whether to jump ship or not for most of your holidays, effectively ruining your time to potentially relax for you.

Just don’t do it.

Remember guys, don't make a bad impression. Keep your Java Scripts in the right place.

So the tests for the AMD RX 7000 GPUs are out. Business as usual: superb for non-RT gaming given the price, crap at everything else - including energy efficiency in FPS/W.

Pro tip to the AMD marketing: you don't highlight features like energy where you suck relative to the competition. You point out your strong points. Admittedly, you don't have much to work with here.

Pro tip: don't get hammered the night before a C# exam because you will regret it

For all those who lurk here and enjoy other people's misfortune - you might enjoy the subreddit justnomil
It's about horrible mother inlaws (and sometimes just mothers) and is great fun to read and get riled up about

Oh China, you still continue to amuse me... in that special way where i somehow both expect it and am hilariously, breifly shocked... then it's somber, confirming what we know is real/continues to be a societal and cognitive decline trend with no apparent rock bottom, without all-out demise as a near certainty... nor a hail mary play.

... but hey, what better way to digest the real-time info, indicative of something that should be terrifying, but is all too expected, than this unique type of format?

Seriously though, even if it worked amazingly, why would anyone be using it outside in public? Does it require several hours a day? If not, and it was a worthwhile result for you... wouldn't you just make it part of your morning and/or evening routine...even if it had nothing to do with aesthetics, that cant be sanitary... unless you also carry it in a water-tight container or disinfectant and typically bring/use your toothbrush and toothpaste mid-day or at unusual intervals.

I have sooo many more questions about this... and none are relative to who designed/mass produced this, nor the quality of the silicone. As it was developed/produced by the silicone factory ive done great, professional, no bs, business with for about a decade... which is why i waited years to publicly ridicule this contraption.

Fyi- their primary product lines are things like bongs and dab containers; im on the fence of it that makes this better or worse.

Creepy personal truth... i reeeeally wanna know how much that woman got paid... and do to my skill set (ie. Im near utter certainty that i could find her and ask her... likely easily abd definitely without being caught doing anything suspicious. Pro tip: publicly declaring things like this makes it a bit easier to not end up doing it... obvious premeditation adding significantly more to any sentencing.

Pro tip for laughing ur ass out.

Watch a you tube video and read the transcript.

Pro tip: write ugly codes to obfuscate code

Pro tip by a Noobie: Whenever you use an open sourced software, and set it up using some tutorial, make sure you download the latest distribution.

Wasted 2 days fixing something while setting up KeyCloak, eventually downloaded the latest version and worked fine. There was a bug in KeyCloak apparently.

Happened the same 2 and a half years ago trying to write node scripts for ElasticSearch, using an older ES library -_-

Pro tip. Don't start to learn react and redux when you have to Support 6 fcking Apps in jquery, plain Javascript and this bad boy Razor. You will kill yourself when you have to work on it. I nearly cried today because of this...

⚠️🚨 PRO TIP 🚨⚠️

ZOOM IN ON TERMINALS + STAGE MANAGER = LITTLE SIDEBAR PREVIEW OF TERMINAL PROGRESS

I don't know about you but I find remembering symbolic link commands too difficult - midnight commander to the resque!

My colleague:
Working in this job double as long as me.

Also my colleague:
isSafari = navigator.userAgent.indexOf("Safari") > -1 (pro tip: almost any browser but Firefox contains Safari in it's user agent, because browsers lie)

Also wasn't able to check if autoplaying a video fails. It's not my primary department, I'm just helping fixing bugs there. They really need an employee with knowledge and experience. The last and only one got fired, so...

To whoever reads this, I hope you didn't take any software development related career to make a living working for others

If your software development career pays the bills by working for others, you'll find devRant a place like heaven

If your software development career was taken to do your own stuff, congratulations, you made a really nice choice, you might be poor, but happy

Pro-tip: ConwaySort is the fastest sort

Pro tip on how to debug?
.
.
.
.
.
.
.
.
.
Throw your slipper right at it.

1. Speaking strictly physiologically, masturbation and intercourse orgasms aren't that different in what it feels like down there. The only difference is what it feels like in your mind, but that depends on your partner and your compatibility.
2. Fleshlight Stoya edition obliterates everything that breathes in terms of orgasm power, except for one single blowjob I received from an autistic mind-reading trans boy. But he's rare.
3. If you wonder whether no-fap or no-orgasm lifestyle has benefits, it doesn't. My high score is three months without orgasm. After two weeks, you stop thinking about sex. Morning wood disappears completely. You have considerably less energy, and every time you ask yourself why, you remember: “ah, it's that no orgasm thing.” Then, it's quite hard to go back to having sex — your penis just won't go up.
4. Sucking your own dick feels weird, just like tickling yourself. It's hard to focus, and the pleasure is next to none. If you always wanted to do that, you can forget about it — it's not worth it.
5. If you're a penis person, high quality anal orgasm is THE best physiological feeling you can get without drugs. Totally blows anything penis-related out of the water, including edging and other advanced techniques. If you chase self-exploration and wonder what your mind/body are capable of, definitely try it, though you have to find an experienced partner & be patient with your body.
Pro tip: if you're a man in a traditional monogamous relationship (if so, what are you even doing with your life?…), it might be easier to convince your female partner to allow you having affairs with penis people than to go full polyamorous mode.

Pro tip for XAML binding:

Set your data context before you initialize the component!

Otherwise the component will render with the default values for the properties.

Pro tip:

Don't make stateful singletons. Just spent an entire fucking morning debugging because one of those fuckers was trying to use prod, and not the demo environment.

WFH pro tip. Wear 3M Worktunes and face a direction that has no distractions.