1. Have some issue with my code which spits out cryptic compiler error.

2. Ask on stack overflow, Reddit, etc for a solution.

3. Get scolded at for "not reading the documentation" and "asking questions which could be answered by just Googling". Still no clue what I'm doing wrong, or what the solution would be.

4. Find someone else's vaguely related problem.

5. Post my problematic code as the answer, with arrogant comment about OP being a retard for not figuring that out for themselves.

6. A dozen angry toxic nerds flock in to tell me how retarded and wrong I am, correcting me... solving my original problem.

7. Evil plan succeeded, my code compiles, and as a bonus I made the internet a worse place in the process.

I think if you tell a bunch of autistic neckbeards that "all coronaviruses are fundamentally incurable", you'd have a vaccine within a week.

"I keep telling you, I'm not a pilot"
"and I keep telling you, you fly boys crack me up!"

I'm not a developer, but I'm doing some complex things and I need the benefit of computers to work things out, so I know enough programming to get me by. Recently one of the uppers decided that all the amateur spaghetti python programs I'd quickly slapped together should be developed into tools that the clients engineers can use!

"How long do you need!."
" I have no idea how to make something like that",
"but it's all just maths right! you can figure it out",
"probably, given long enough bu.. "
"okay get started and we'll check in in a couple of weeks" "hold o.." "I'll give your pride and joy to the graduate to fuck up while you're working on that" "wai.. " "anyway got take this call, good luck"
┗|｀O′|┛

So here I am.. I have no idea what I'm doing.

So since I have a working knowledge of python, fortran and VBA, someone suggested I learn nim, which was not what he sold it as. Then a software engineer that went to the same uni as me, suggested RUST! you can't mess up rust, and look at this I created (shows me a decent looking desktop application) "I'll help you out". But it wasn't really that easy.

Then I asked some questions... that was my first mistake, that's not acceptable until you know what you're doing apparently. Especially when the answers are in the docs you can't find in a topic you don't understand for a version you're not using solved with a tool you've never heard of for an operating system you forgot existed. Look at this moron asking a question.

Okay to be fair, I went through the rust docs and it was well written, and I do really like this language. But I do not have a degree in computer science, and so many docs for crates are just written with an expectation of a certain level of knowledge. As soon as there's a build error, it's at least 3 -4 days of me faffing about trying to decipher hieroglyphics.

..and the graduate is about to unwittingly commit manslaughter..

I'm sure whoever needs to fix this mess in the future will post a rant about this train wreck.

I really hate search engines sometimes

I don't usually post memes, but this one is just a little too on the nose.

Recruiter: "Do you have at least 5 years of experience with Angular?"
Me: "No, barely half a year"
Recruiter: "Then why did you get in touch with me?"
Me: "You were the one calling me [you moron]"

Things I'm half decent at: Writing code
Things I am absolutely the worst at: Managing projects

Things I got employed for: Writing code
Things I do: Managing projects

I was expecting a 4th interview this afternoon for a position as a fullstack elixir developer.

Got a response from the CTO.
'Even if you pass all the tests with success, we could not go further because you're a junior and we're looking for a senior'

Well, dude, you've seen me 3 times and didn't understand that I was a junior ? My CV is not enough explicit ? It's written at the top of it...

So after a motivation interview, technical test, technical interview and Phoenix framework interview, they only realized yet the plot.

Good luck for your seniors to pass their knowledge to other seniors.

A lot of docker containers.

I often have to use docker containers while I don't understand it as well yet and quite some containers literally come with zero documentation or bad docs.

This both as for how to set the containers up and how to debug stuff.

This is one of the big reasons why I'm not as big of a fan of docker yet.

🤔🤯

I'm convinced this is going to be wildly unpopular, but hey...

Please stop writing stuff in C! Aside from a few niche areas (performance-critical, embedded, legacy etc. workloads) there's really no reason to other than some fumbled reason about "having full control over the hardware" and "not trusting these modern frameworks." I get it, it's what we all grew up with being the de-facto standard, but times have moved on, and the number of massive memory leaks & security holes that keep coming to light in *popular*, well-tested software is a great reason why you shouldn't think you're smart enough to avoid all those issues by taking full control yourself.

Especially, if like most C developers I've come across, you also shun things like unit tests as "something the QA department should worry about" 😬

If you want to learn about bad UX design, look at every GDPR-compliant cookie alert on websites. The dialogues generally follow this pattern:
* Highlighting "Accept all" instead of "Reject" to bait you into habit-clicking.
* After clicking "Reject", you'll be redirected to an infinite list of usages. There is never a "deselect all" option. You need to opt-out everything manually.
* Sliders use some ambiguous coloring scheme without labels, which means you never know if you turned it on or off.
* Instead of "Reject", there is an "Other options" button. Clicking it redirects to a EULA document, with at the end... no other options.

Everything looks compliant, but they are still boobietrapping everything so you just wouldn't be able to opt out. Fucking data-vendoring assholes.

What can I say 🤷

A typo today has rendered me the joke of the office... 😂

Almond's PR: "Added missing unit testes to classes Foo and Bar"

----

Bob: "LGTM. Bet that took some balls."
Craig: "LGTM. Missing unit testes drive me nuts."
Ian: "LGTM. Write your testes with your code guys, a bit bollocks to have to add them afterwards."

New job with 100% remote work. They don’t have a laptop sent. I am paid to wait for a delivery.

I tried DuckDuckGo like two years ago and my opinion was “meh, I don’t like the results”.

Yesterday @Root made it clear that the sole amount of data collected changes the whole perspective of tracking.

I went to shower thinking about that and as I was standing there enjoying warm water...

It hit me.

I liked google results and disliked DDG not because DDG was worse.

I liked google results because they were CRAFTED for ME to LIKE them. They exploited my confirmation bias, the strongest of all biases.

I took my other phone which is android, has a different sim that isn’t tied to my identity (don’t ask, this is Russia), was never connected to my WiFi and of course has no google account tied to it.

I tried googling stuff.

The results was just like what DDG gets you, the only difference was google amp were on top.

The fuck. One of the wokest moments ever.

How the fuck does these testers find these bugs
there are like
- go to this
- click on this
- type the first 57 digits of pi
- sacrifice your first born to the devil
-> there the table is misaligned by 13 pixels, fix that

The Handover!

No comments allowed in JSON pisses me off so much.

Sure, I get all the arguments of "it's supposed to be a data-only format for machines", "there are alternatives which support comments", and "you can add comments and then minify the file before parsing"

But right now, when I just need to put a quick note inside a super confusing legacy package manager config about why certain dependencies to be frozen at a specific version, IT FUCKING PISSES ME OFF THAT I CAN'T JUST ADD A FUCKING COMMENT.

This thing I've assembled during a long online meeting

This made my day!

Mark.

Mark was a support guy who could have been replaced by a robot. Nearly every support request that came in, whether it made sense or not, had a reply saying:

"Thank you for your query, I will escalate with the development team"

...and then I would have a message saying:

"Hi Almond urgent issue case xxx - I think you need to PLEASE CHECK LOGS" (yes, with that capitalisation.)

I'd then look at the case, take 10 seconds to work out the customer had done something stupid when calling our API (often forgetting their authentication details, despite a clear message telling them as such) and tell Mark what the issue was, and how to find it for himself next time. I'd then usually get:

"Thank you but PLEASE CHECK LOGS to see if there is any more info we can provide to customer"

...there would be more back and forth, and then eventually something like the following would reach the customer...

"Very sorry the development team have a major issue they will fix very soon but in the meantime a workaround is (instructions for using authentication details)"

🤦‍♂️🤦‍♂️

CSS quick maffs:

Using viewport units to define font size but sometimes it's too small?

Instead of font-size: 10vw;

use font-size: calc(10vw + 20px);

This will make sure that font size is AT LEAST 20 px no matter the viewport width. Treat the resulting font size like a function of viewport width and feel free to experiment with it. With calc in that case you can achieve the best typeface responsiveness possible.

Dear mobile apps devs,

No one's gonna hate you if you do not provide a multilingual support. Just, please, stop using Google Translate and force the app's language to the phone system's. It's just dumb

Sincerely,
A non native english speaker

Wanna mess with users? Take

“OK” and “Cancel”.

You know what looks visually the same but means the opposite?

“NO” and “Confirm”.

Deploy that little ui update overnight and watch the world burn.

Wasn’t hired once because “we are startup and we don’t like your favorite meme that much”. Yes, this is what happened.

Their company was gone in two months.

They said my favorite meme wasn’t so nice
Their bodies are now food for the mice

Looking at code in our workplace.. I realized one thing. Like Devops, legacy code is actually a mindset.

So here goes my thought:

A piece of code is not legacy because it was written ten years ago.

A piece of code is legacy because it looks like a piece of legacy code.

With the legacy code mindset, you end up writing legacy code no matter where you are, when you wrote it.

I was looking at some part of our code which we written in just the last few months, and I can’t help but think that they were legacy, so it really doesn’t matter when it was written!

It is more about how you write your code that determines whether it is legacy :)

Hopefully this was not crazily confusing anyone. Have a good day guys & gals!

Companies: We can’t find any senior developers to hire.

Also companies: We pay seniors like juniors.

Who else has the problem of wasting more time as you get more free time?

Searched stackoverflow and found the exact issue I was having. The question is from 2014.

The accepted answer is a messy hack. Fuck.

The second answer is clean, clear, concise. It was posted 38 minutes ago.

Is this real life?

Piece of shit cake. I'll stab you in the goddamn virtual neck with a screwdriver. Not get my nuget packages. Go fuck yourself in your fat fucking ass. Goddamn, who automated this build process. I did. Fuck me.