One of my theoretical CS teachers always complains and makes it sound like everything around him is an annoyance to his existence
- being late or in a bad mood? His pregnant wife is very tiring (good ol' haha women are hormonal much?)
- having to create and correct exercises for us (students) is a nuisance because it's so much work and we're not supposed to be spoon-fed (which makes the whole learning experience very demotivating)
- every explanation start is continued by at least 3 changes in the explanation itself, which makes everything super-confusing
- all his helpers are incompetent and not rising up to his expectations

Someone needs some self-reflection

If my previous rants about my job didn't convince you, I don't know what will...

Don't do like my work supervisor:

Step 1:
*gives task*
Me, starts working on task early in the morning
*task requires his interfering, and is stalled without it*
Me, messages supervisor

Step 2:
*supervisor takes the whole work day to reply, saying that he didn't have time to look into it*

Step 3:
Me, does almost nothing at work the whole day; closes laptop upon seeing the message of the supervisor

Step 4:
Profit: go home early

- my (non-dev) supervisor at my job
- no documentation
- no source control
- people working in the same team with completely different programming/domain knowledge levels, but also very different ways of being
- bad within-project communication

Luckily not all of them are about my job. We do use source control.

Talking about bad error messages

I missed the regular enrollment period for courses starting in 2 weeks, but I did have late enrollment days, which I remembered.
When wanting to late enroll, I was greeted with th error message in the picture. Bad news first, good news later I guess

As you can imagine, my heart skipped a beat. Nonetheless, it was all good in the end, because I was already enrolled for the compulsory courses I wanted to take

New project at work involving Google Nest Hubs, supervisor asks me to do the initial setup of one of them to start developing with it using its API.

I start looking throughout the documentation and realise that we need to setup a work google account in order to register the devices, pay a fee and only THEN be able to use Google's API for Smart Devices (damn, you, Google!). Supervisor is somewhat baffled by this, and in my head I'm also surprised by his reaction. I'd assume you'd research your devices before you buy them, right?

Later, he comes into the room I'm in (I'm still allowed to work on location), looks at the freshly setup Nest Hub, saying "wow, this sure is a much smaller screen than I was expecting". I mean, you did research these devices before you bought TWENTY of them. RIGHT?!

On my way to fight with this Google device-registration-API-thing now.

To be continued...

Most probably the short time pressure and the mindset of "in these x hours/days, I can't do/think/be interested in anything else but the hackathon". It feels like it significantly disrupts my daily flow

- participate in more exciting projects
- be more mindful about the time and mental resources I put in my projects
- find out what kind of dev I want to be

Best: building a compiler in C and using LLVM as an IR tool

Worst: my job, and a group project of 5 people which I ended up working on alone

As someone deeply questioning their life and career choices as of now, I wouldn't want to become a dev anymore because:
- you spend most of your time burning your eyes on a monitor and getting terrible back pain
- you might sell your soul to company benefits whose only purpose is to make you distracted from the fact that you're basically spending 1/3 of the day wishing you were doing something you actually want to do
- might have to do some exhausting communication ooga boogas to understand what supervisors and your other colleagues want to say (in a small company setting)
- again, as in my previous rant, if you're not on some less disposable dev position, you could as well become something else given that junior salaries are not that high
- get into an unhealthy work world where little hours of sleep, overworking, and other such unhealthy lifestyles are praised or used to determine your worth

Of course, these differ on a case by case basis. I'd become a train driver or something if I still didn't have to eat and not throw more money at a career change
Life's tough

I was told there's gonna be:
- good salaries
- informal company setups with benefits
- lots of jobs available
- non-dev people look at you in amazement
- get to work on really interesting stuff

What I'm actually doing:
- carrying a team of people in uni because you're the only one who knows how to code
- deal with shitty uncommented legacy code at work
- be reminded that if you don't do something super-sophisticated you're easily replaceable
- spend unpaid overtime hours because you're the only one at your job that is on the issue (I see a pattern of being alone in a problem here)
- requestion all my career decisions
- cry and be stressed
- hate every minute of work, yet be stuck in it because it's a source of income that is flexible enough for me to be able to study full-time

So dunno man, I'm still waiting on what I've been told, people say there's lotsa money and satisfaction waiting for me after grinding through 5 years of high education, it'd better be worth it

I got their financial support to pursue higher education in CS and move abroad.
However, I've never really got their constant emotional support. Each decision I was taking, I always had to prove myself, which can be tiring and unmotivating, since I'm expecting uncoditional love and support from my parents, not an interview and a selling pitch for myself every time I tell them something

A bunch of pictures of friends, a train dev duck, a wooden train toy, a pair of demon horns, a tiny hand

Been working for a while with some terrible code with no documentation that I just inherited from a previous employee

Topic: multi-threaded program in Python

Goal: kill both parent and children with keyboard interrupt

Intuitive idea: check in children processes if parent still alive

Implemented idea:
- parent creates socket connection
- keyboard interrupt kills parent and thus the socket connection as well
- children receive some specific socket error from the loss of connection
- children catch the exception and are killed
In Python 2, of course

I, too, like to inflict pain on myself for fun

I remind myself that nobody knows everything, and even the most knowledgeable people have their gaps in knowledge.
For whatever I'm not doing well right now, I'll keep an open mind, and be willing to accept advice and work on it.
In the end, just because I'm not doing something right once, doesn't extrapolate to the rest of my life. I still try to be the best version of myself.

Geez, I'll be getting out of this quarantine as a stoic mindful person

- not seeing and hugging my colleagues (I miss hugs SO much, with everyone)
- everything being online, which makes it less serious and more like a game I can just turn off. It makes it very hard to keep myself motivated

- hold yourself accountable for your mistakes
- keep track your mistakes and learn from them
- put thought in what you do
- be organised
- become comfortable asking for and offering help
- realise that some problems have no universal solution
- don't just copy what others do, but also think for yourself
- learn to be patient

Sometimes I get inspiration for pole choreos, so I can take a break to try it out. I don't even have to change from my pole outfit

Anything related to UIs or data science
That, working with a spaghetti codebase, or unhelpful and not nice teammates

Not dev-related, but it's always the every day schedule optimisations that are satisfying. If I need to be in various places throughout the day, change different types of transportation, etc., I always think about the optimal route and time-planning such that I have the least overhead, visit the same place as few times as possible (usually my home, since I live far from most of my daily activities), take the shortest routes and be on time
The same applies to taking public transportation in my hometown. There is no clear schedule ("arrival can vary between 10-15min", no app available to tell you about it in real time), yet by living there for so long, I figured out when certain buses/trams leave based on the ones that are already passing me and the time of the day. This way, I know which buses/trams to take and change and get where I need to be, without even having an app or a clear schedule (of course, unexpected things like buses catching on fire can always happen)

A few months ago I ranted about how my first encounter with Assembly was hopefully the last one

Here I am, again, with my second Assembly encounter. However, this time I'm able to read and understand it more, such that I'm even able to compute stack layouts. I don't even hate it that much anymore.

I guess I'm walking the path I couldn't defeat

*cries in %rax*

All my university projects technically hold up to coding for the least amount of money - the tuition fee I have to pay, which is always a minus amount of money

Quite a blurry one. Currently going to uni to dip my toes in some of the subfields of CS. Until now, I found more things that I wouldn't want to do than I'd enjoy.
Ultimately I just wish to sit at a desk and program all day, preferably for a public transportation company (read/hope: railway company), ideally on the route scheduling side

However, it would be nice to know what I wish to do dev-wise on the shorter run besides uni and side-projects :D

I normally just have nightmares about the projects I'm working on, especially when I struggle with a bug for days. Those are usually about just me stressing out about it. However, I have a lot of dreams about computers/technology, not necessarily coding-related:

- datacenters were just potato fields. If you go work the field, you'd go data mining

- in Biology, when being taught how having children works, you only tell that "parenting is only chmod-ing the rights of your children until they become the owners themselves"

- IP addresses with emojis instead of numbers were a standard now and they actually managed to replace IPv4, because everyone was so into emojis. They named it IPvE

- I witnessed a new Big Bang when the 32-bit Unix time overflown in 2038, and we were all quantum bits

Currently trying to convert a Python (2.7) framework into its C++. Surprise, surprise, the C++ APIs are also all deprecated

"Here's a guide to creating your project using our non-deprecated framework, except it will still call our deprecated methods under the hood"

Additionally, I had to make this framework work with OpenCV, which was complaining about my C++ framework being deprecated and not being able to link to missing modules (which were already installed).
All of this has eaten 4 hours of my life, I could as well throw the laptop out of the window

"Try reinstalling the missing modules separately"
*installation takes less than 1 minute*
*runs build again, everything work*

I'm done for today *flies away in desperation*

Haven't used it since and hopefully never will again, but understanding recursion and keyboard input in Assembly (uni project)

After a long (4 days) sleepover with my friends, with 14 hours a day of slamming our heads against abstract registers, we could finally program the factorial and take floating numbers as input and output them on the screen. It was nothing but pain, but the moment we got it, the sky had opened before us :D

Never again

The classic "using Windows Firewall" joke

My friend dropped her phone and it doesn't turn on anymore, but she has a dual-SIM spare phone. So the problem didn't seem too bad at first. I told her I'd help her with the backup restoration, set everything up on her new (old) phone.
After 30mins of trying to restore the backup from her old phone and moving the SIM card to the new phone...

"But I didn't have a backup and the SIM card tray isn't working. Can you also help me recover my 10 000 pictures and songs?"

I guess I'm done here

1. I love using it for automation and creation of new stuff
2. I'm a visual thinker and working with abstract things. The process of thinking about a program and developing it is especially rewarding and exciting for me
3. I especially like using it in relation with Maths for algorithms and scheduling, which is tightly related to (2), but also to the fact that I love Maths

There's a café right next to the water and I can see boats arriving and leaving in the harbour. This peacefulness, but also that I can hear the mild voices in the background is what does it for me and my focussing. Sometimes I also go there with friends, as it's always nice to have live debugging ducks :D