Y'know what.
Fuck all the political posts here,
and fuck all of you who see them as a opening to spout your counter arguments.

Best Dev experience: Switching to rust,
Worst Dev Experience: Using VS code at work because I can't get anything else approved to be installed.

I'd say;
Python is Slitherin,
PHP is Hufflepuff
C++ is Griffindor
><> is Ravenclaw

Yay or nay?

Another startup is about to go into the drain because some clueless fucking exec prioritizes "innovation" over *actual fucking income*. If a clients ask us for something that is simple as fuck-- you're supposed to say "sure, thanks for the free money" not get your ego up in their face, and tell them to fuck off because "we don't do standard things". You're risking a hundred people's jobs and everything *I* have worked my arse off for, just so you can play at being a budget Elon Musk.

I just drink until I think I am.

Devops is an HR/management wank-word.

Of course we all know that devops is a lean, next generation, best-practice, shifting focus towards actionable items to facilitate value added integration and synergy between two key silos of the company.

To anyone new to the corporate world I have this advice: there's a game no one tells you about in school or university. It's a game of politics. The good news is that you can choose not to play the game. The bad news is that others who do can change that decision for you, if you give them a reason to. So here's my tips to keep yourself from common bad situations:

* Some people will say they'd "prefer that people were honest". This is an outright lie.
* Be guarded - if a scenario could be taken out of context assume it will be.
* Mimic the office culture, don't try to rock the boat.
* Be polite, but always stay neutral between colleagues, picking a side means you're playing the game. Unless that side is your company vs another company in which case-- you are 100% on the company side and everyone else is stupid and incompetent.

When you finally get to use that tensorflow side project you've been working on for a while to solve a real world problem and your boss wants to know how it works.

About a decade ago there was a torrent site for audiobooks audiobookbay I think?, if you forgot your password to your username they would literally just give you a new password on the next page. Naturally being a 1337H4X0R teenager I found the username of one of the admins and got into their account on the site. I don't know if they ever fixed that but that was a serious wtf moment.

Edit: just checked this flaw has not been patched.

The way I understand software licenses.

Cool bro MIT: Free to do whatever you want as long as you include a copy of the license and you can't hold the original accountable.

fair dude Apache 2.0: Like the MIT license but more bureaucratic and few more minor things you need to keep track of.

scumbag GPL: free as in the same way that prison food is free. used by java in gotcha cases as a source of revenue because no one understands java licensing. Often used in the form of a deterrent so you never dare to open up the github page.

scumbag GPL who, realising they have no friends, becomes slightly less of a dick LGPL: But please stop using this and use our more restrictive "freedom" license.

I am not a lawyer. This is not legal advice.

Instead of ;
I end lines with ; //FIXME

"I have a great idea for a messaging app.
But I can't tell you what it is until you agree to make it for me, I can't pay you right now but I'll pay you back when we make tonnes of money!"

My startup idea: you create apps for people with bad ideas and the fees on a 1 year 'loan' with high penalties for failing to pay. Fair right?

Strings in most languages:
(☞ﾟヮﾟ)☞ foo: string = "bar"

Strings in rust:
(╯‵□′)╯︵ AHHHHHHH!
borrowed value does not live long enough
types differ in mutability
cannot assign twice to immutable variable

"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.