I didn’t. I went for an interview and quizzed this multi-million £ business about their architecture: it sounded awful.
I made some diagrams on how I would’ve done it, how it would scale etc and why. They were blown away and wanted me to implement this structure including the job they wanted to hire me for.
They sent a contract over: had the wrong name on it
They corrected the name but I noticed the salary was incorrect
They sent a third and by this time I was offered an interview elsewhere so I went

The hirer then called me to say he was frustrated I hadn’t signed a contract yet making it sound like it was my fault for not wanting to sign an illegitimate contract. he then went on to say that the salary had been reduced, I asked why and they said they felt I wasn’t a senior developer.
So I took the other job and they kept their shitty architecture 💁🏼‍♀️

Last month: Opening devrant
Facebook, Mark Zuckerberg, FUCK FACEBOOK, ZUCKED ME, KILL MARKBOOK, ATTACK FACEBERG

Last week: Opening devrant
GDRP, GDRP, GGEEDDEERRPPPEEEEE, FUCK GDRP, YEEEY GDRP, WHY GDRP, UPDATED OUR GDRP, FUCKED MY GDRP, PEED IN MY GDRP

this week: Opening devrant
Microsoft, Github, NO Microshit, Burn Github, FUCK GITHUB, POO ON MY MICROHUB, VOMITED ON MY GITSOFT

next week:????
(Google, you better be ready, it's your turn)

yearsLeftToDeath--

website: uwu,,,im sowwy, but pweaese...wiww you pwease tuwn off ad bwock? we weawwy need ouw money (´･ω･`)

me: ok [turns off adblock]

website: 𝐃𝐎𝐖𝐍𝐋𝐎𝐀𝐃 𝐂𝐔𝐍𝐓 𝐖𝐀𝐑𝐒 𝐓𝐎𝐃𝐀𝐘 𝐇𝐀𝐕𝐄 𝐇𝐀𝐑𝐃𝐂𝐎𝐑𝐄 𝐒𝐄𝐗 𝐖𝐈𝐓𝐇 𝐓𝐇𝐄𝐒𝐄 𝐂𝐀𝐑𝐓𝐎𝐎𝐍 𝐆𝐈𝐑𝐋𝐒 𝐈𝐍 𝐀 𝐕

If you hold a Unix shell up to your ear you can hear the C.

Historically, tattoo artists would operate free of charge on women's breasts. This was an attractive offer for both sides, and spawned the phrase "tit for tat", which now represents two sides of an argument offering items of equal value.

This is a fact I just made up, like "Java runs on 4 billion devices"

Hey, first time poster :-)

Working alone on a C++ app that has to control a GUI, camera and electronics on the side... but between the test cases, switching between classes and helping colleagues on unrelated issues, I find it hard to keep track of what connects with what, what needs to be done, what IS done...

So, how do you guys and girls keep track of your projects ? Stuck with To-do lists for now ^^

Ffs can you not

Different error is better 👍

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