Already wrote about wk92 but i have to add:

STOP MAKING ME ATTEND COURSES SO I AM EVEN ALLOWED TO TAKE EXAMS.

Like what the hell. You know when it comes to networking i'm doing okayish, coding straight A and then there is maths, let's not talk about it. BUT FFS I WAS NOT ALLOWED TO TAKE 2 OF MY CODING EXAMS THIS SEMESTER CUS I DIDN'T VISIT 2-3 EVENTS OF IT.

I am a coder. I aspire being a coder. I study software development. I just need to prove myself and some dudes can do it. Let me do my thing.
Btw, there weren't any mandatory events for maths. Of course. Why should there be. Yeah okay

My boss drives me crazy. He hired me for working on his SDK which is game related. So I am responsible for basically everything, including an ingame UI (menu etc.) and to predict the future path of a game object (unit, minion, ..) when a certain spell is casted on it. For that task I divided the prediction into firstly getting the predicted path of the unit without a spell being casted and then a class that would cast the spell on that path and estimate the units reaction to that cast. Simplified, but that way you get a pretty okayish result. Now he thinks that is too complicated. "Can we not put everything into one class, if someone wants to replace the prediction he needs to read documentation for hours". WHAT THE FUCK DID YOU EXPECT, THAT IT'S GONNA BE SOME ONE CLASS 3K LINES MAGIC??

Same for the GUI. We only have DirectX and don't want to use a framework. Guess what, it's more than one class if you want to seperate view, model, controller or whatever fucking "design pattern" thing you use.

And then Git... he seriously said let's not use branches till release, I feel like they slow down things.. before I was there they did every operation on master.

And if it was just that..

/rant

I put much work into this, time to leave?

---Startup Rant---

Being a senior developer doesn't grant the privilege to join a team and starting a drama out loud that everything is bad and you don't like it.

First, if everything is perfect there is no need to hire you.
Second, think about the value that you can bring to the team instead of making them feel bad, how can you prepare an improvement plan and start to learn the factors and reasons behind those decisions.

What's funny, it that the same guy after a couple of months starts introducing bad fixes and he says it's ok for the moment, it's not good but it's okayish, I wish I had a time machine for those developers!

It's asked before here but need to be questioned again because I'm bored.

Would you rather have fucked a sheep while no one knows or that you didn't do it but everyone is sure you did?

The sheep is average looking with okayish BMI. Looks bit German

Top do-over... I was extraordinary in biology and microbiology. For some reason, I still remember every little detail, everything that I was learning regarding it felt so natural and easy for me. My heart was pulling me to IT, in the end, I become an average, okayish IT guy, with reasonable programming, networking, and other IT skills, but I had to suffer the hell out of studying to reach here. I never was in love with biology, but damn, it frustrates the heck out of me that I'm so freaking good at it... So, my do-over would be to go all-in with Biology.

My masters final project and had only one girl in my group who could do front end. 3 months to do it and after 2 months we don't even have a landing page. Had to make a okayish looking design with another teammate.

Good code is a lie imho.

When you see a project as code, there are 3 variables in most cases:

- time
- people / human resources
- rules

Every variable plays a certain role in how the code (project) evolves.

Time - two different forms: when certain parts of code are either changed in a high frequency or a very low frequency, it's a bad omen.

Too high - somehow this area seems to be relentless. Be it features, regressions or bugs - it takes usually in larger code bases 3 - 4 weeks till all code pathes were triggered.

Too low - it can be a good sign. But it should be on the radar imho. Code that never changes should be reviewed at an - depending on size of codebase - max. yearly audit. Git / VCS is very helpful here.
Why? Mostly because the chances are very high that the code was once written for a completely different requirement set. Hence the audit - check if this code still is doing the right job or if you have a ticking time bomb that needs to be defused.

People
If a project has only person working on it, it most certainly isn't verified by another person. Meaning that only one person worked on it - I'd say it's pretty bad to bad, as no discussion / review / verification was done. The author did the best he / she could do, but maybe another person would have had an better idea?

Too many people working on one thing is only bad when there are no rules ;)

Rules. There are two different kind of rules.

Styling / Organisation / Dokumentation - everything that has not much to do with coding itself. These should be enforced at a certain point, otherwise the code will become a hot glued mess noone wants to work on.

Coding itself. This is a very critical thing.

Do: Forbid things that are known to be problematic in the programming language itself. Eg. usage of variables in variables, reflection, deprecated features.

Do: Define a feature set for each language. Feature set not meaning every feature you want to use! Rather a fixed minimum version every developer must use and - in case of library / module / plugin support - which additional extras are supported.

Every extra costs. Most developers don't want to realize this... And a code base that evolves over time should have minimal dependencies. Every new version of an extra can have bugs, breakages, incompabilties and so on.

Don't: don't specify a way of coding. Most coding guidelines are horrific copy pastures from some books some smart people wrote who have no fucking clue what you're doing and why.

If you don't know how to operate on people, standing in an OR and doing what a book told you to do would end in dead person pretty sure. Same for code.

Learn from mistakes and experience, respect knowledge from other persons, but always reflect on wether this makes sense at this specific area of code.

There are very few things which are applicable to a large codebase on a global level. Even DRY / SOLID and what ever you can come up with can be at a certain point completely wrong.

Good code is a lie - because it can only exist at a certain point of time.

A codebase should be a living thing - when certain parts rot, other parts will be affected too.

The reason for the length of the comment was to give some hints on what my principles are that code stays in an "okayish" state, but good is a very rare state

What attracts coders to open source libraries?

If you ever contributed to open source projects, what was the reason?
I am contributing to my supervisor’s package which is really handy for biophysicists (quantum mechanics). It is basically tons of code in python, it has okayish internal design, coverage 39% and B+ codefactor. I wish we could get more attention from scientists in our field and attract people to contribute to our project.

I had a job opportunity with okayish maybe good job and more money. Last november. But i had a bad feeling somehow. I told my boss and he said he will try to get a raise for me of i stayed, so I stayed. He wrote some stuff so mgmt to hopefully get my raise.

Meanwhile super important project took place. I have to meet deadline, this friday. Was somewhat motivated, did a lot of overtime.

Today mgmt responded, raise denied. Because i can not prove i have an open opportunity with that salary. No shit after it took them two months!

And the day after tomorrow is the deadline. Bad timing, suckers, bad, bad timing. I will deliver what i have regardless how buggy tomorrow and take friday off.

A classmate I haven't seen in 2 years popped up in my Linkedin.
I looked up her profile and it seems like she now works at SWE in okayish company after an internship in a prestigious company.

This throws me a little bit (I am jealous obviously). We've worked in the same uni project before, she's okay when it comes to theoretical courses but a bit behind when it comes to anything related to computer. I would never think of her working as SWE as she did better in traditional engineering (think Civil Eng, Mechanical Eng etc, Aerospace Eng.).

And yet I heard a lot of people online complaining about difficulty of finding graduate/junior position. If a person like her can find something, surely someone with pure CS background should find something easier. But then again, job hunting is 50% pure luck. I have concern on the quality of work that she will produce, but maybe I underestimate her a lot? 🤔

Why does snapchat on android suck so badly?
Lemme get this out of me.
They admitted to focusing on the iOS variant more from now on. Why? Becuase it has a larger user base.
That means they will not give many fucks about the ONE BILLION ANDROID USERS.

But about the app itself...
With quite normal usage (let's say around 30 minutes opened in total, daily) snapchat uses more battery than my screen. What the fuck?
It is literally at the very top.
It might go up to 800mAh calculated drain. I don't know how they did it.

Anyways, it doesn't even work well.
It has a lot of lag, crahses, and makes my phone as hot as a cup of tea.
I suspect that's becuase it keeps using the camera. That is, keeps it on even when you are on a different screen. This is bullshit. I do sometimes chat with people on SC but I try to minimise it for this reason.

The UI itself is okayish but still lags beyond comprehension in comparison to other apps (wow, I love the android discord client, it has full functionality at low resource cost).
As far as I'm concerned it uses some sort of web technology mix. It does use chromium so I suspect HTML, CSS and JS is also present in the source code.

Also, let's make this a terrible mobile apps rant - feel free to contribute.