I'm at my seat during the regular morning routine of checking emails, planning the things I need to complete/study when my phone rings.

HR: Good Morning, can you come over to the conference room please ?

Me: Sure

I enter the conference room and on the other side of the table, I see a group of 3 HR Managers (not a very nice feeling), especially when it was 10 months into my first job as a Trainee Software Developer.

HR: The company hasn't been performing as expected. For this reason, we've been told to cut down our staff. We're sorry but we have to let you go. You've been doing a great job all along. Thank you.

Me: ---- (seriously ?!)

The security-in-chief 'escorts' me out of the premises and I hand over the badge. I'm not allowed to return to my desk.

This happened about 16 years ago. But it stuck with me throughout my programming career.

A couple of Lessons Learnt which may help some of the developers today :

- You're not as important as you think, no matter what you do and how well you do it.
- Working hard is one thing, working smart is another. You'll understand the difference when your appraisals comes around each year.
- Focus on your work but always keep an eye on your company's health.
- Be patient with your Manager; if you're having a rough time, its likely he/she is suffering more.
- Programming solo is great fun. However it takes other skills that are not so interesting, to earn a living.
- You may think the Clients sounds stupid, talks silly and demands the stars; ever wonder what they think about you.
- When faced with a tough problem, try to 'fix' the Client first, then look for a solution.
- If you hate making code changes, don't curse the Client or your Manager - we coders collectively created a world of infinite possibilities. No point blaming them.
- Sharing your ideas matter.
- Software Development is a really long chain of ever-growing links that you may grok rather late in your career. But its still worth all the effort if you enjoy it.

I like to think of programming as a pursuit that combines mathematical precision and artistic randomness to create some pretty amazing stuff.

Thanks for reading.

I put a lot of work into trying to explain to you muggles what I do all day in a way you can understand (it's hard, trust me) and you still reject it as boring nerd crap. I'm sick of it! What if you told me working at that restaurant is "putting water on plates, wiping it off, and putting meat and cheese between slices of bread" and I said "wtf is that, and who cares?" Wouldn't that hurt your feelings, that I didn't even attempt to make a connection with you, friend? That I didn't even attempt to step outside my experience to meet yours? Isn't it equally insulting how far you have to dumb it down, just for me to lose interest entirely? And yes, I know that's not your specific task. That only proves my point further.

And why, exactly? Conceptually, you handle pre-digested poop all day.
_I teach plastic to think._ Sometimes it even thinks better than you do.
How is my job less interesting?
And what's more, why does EVERYONE seem to think so?

How do you expect people like me to keep your iPhones, bank accounts, and self-driving cars working if you alienate us like an alternate species for building those things? I mean really. You people treat us with a disinterest harmonious with homophobia. "Don't ask, don't tell." Except you do ask. And then you condescend as if working with my brain makes me less worthy of your attention than your exciting minimum-wage restaurant job.

Have fun with that, by the way.

Oh, and you're welcome for <object I fixed that wasn't really broken>. Maybe next time, just google it.
I know you won't.

Today's my lucky day for job rejections...

"Unfortunately we have decided not to proceed with you as a candidate because the salary range you expect lies outside our budget."

That's very interesting indeed because in the very first interview (phone call) you asked me about that range and I gave it, straight and simple.

Then I had to do a coding challenge, which I usually refuse, but did anyway. It took about 15 hours. Let's not forget that it had nothing to do with the job I was applying for, but OK.

After that, a second interview, which took 1.5 hours and a third, which gobbled up 2 hours of my time.

Then you tell me that you're not willing to fork over the dosh, after having wasted 18.5 hours of my time!

Thank you very much, you anus blossoms!

"full stack" means "you'll be doing everything from gathering client requirements through data architecture up to the UI design and of course implementing all of it"

"backend" means "you'll be coding everything from database through server-side code and client-side code including html and css"

"we need you on-site all day every day" means "we have no idea how and why we should use repositories with remote access despite being a company developing an internet app, and we don't trust that you would be working anyway"

"interesting challenging projects" means "the same boring crap as every other company, running on an incredibly botched and dezorganized codebase".

"competitive pay" means "actual pay is around 1.5 times the minimum allowed pay, and everything else is being siphoned off into (stupid and useless) 'benefits' like massage and fitness discount coupons"

"friendly collective having fun at numerous company events each years" means "it is mandatory for you to participate on our weekend drinking retreats but you'll only find out when we fire you because you're 'not a team player' after you refused to participate on those"

WEB FUCKING THREE

Ok, some of this shit is interesting, let's get that out of the way:

Crypto - great for doing illegal things, great for financial speculation, interesting mathematically. But as likely to replace actual currency as I am to replace the fucking Queen.

NFT - should be written on the headstone of humanity. Entirely fucking useless, planet-roasting bro-wank dressed up as a revolution in...pretending to own shit. The only difference between a Bored Ape owner and my nephew pointing at a castle and insisting that it's his, is that he isn't thousands and thousands of pounds out of pocket by doing so.

Metaverse - AR and VR have been around before this dogshit rebrand, and they'll outlive it.

No, it's not that. It's that we now have a new species of parasite - the "Web3/Metaverse" LinkedIn guru insisting that this shit is even needed, let alone the next big thing.

Web 2.0 was a stupid fucking term alright, but it did represent a new generation of technologies that were badly needed, and adopted by the entire community. Web3 is a bunch of shit that some cunts think they can get rich off, so insist that we need. I wouldn't even give a fuck but I've already spent hours of my life explaining to clients and peers that this is UTTER FUCKING BOLLOCKS, there's no need for a blockchain in your app, there's no need for a blockchain in virtually anything. Yeah if you want some fucking 3d in your app or your page I'm your man, but if you keep saying 'metaverse' I'm going to fill it with easter eggs.

None of this shit was needed before and none of it is needed after. Have you looked at web3 games? It's Steve Buscemi asking 'how do you do, fellow computer games?', it's a fucking gambling app pretending to be something a human would do. Clash of Clans and Candy Crush already cornered the market for that type of fucking mug, right now you're making the Candy Crush business model look responsible and efficient. You CUNTS.

This happened a while back but thought it would be an interesting story.

So there is this guy, I'll call him Jack. Jack was a weirdo. He just graduated high school but thought of himself as very hot in terms of dev skills. He boasted lots of good programs, that are the best in industry, except they don't work (like the best proven file compressor, that just can't decompress anything because of some "bugs"). He also entered language holy wars quite actively, saying that Delphi is the best platform ever.

Aaanyway, a couple of years pass. Jack is now a student. Jack tries to make some money, so he talks to some guy, that offers him a "job" at the tax office, where he has to modernize the data infrastructure of the tax authorities. If you think this sounds very wrong, then you're 100% correct. But it gets better. After 2 months of work, the guy manages to do that. It's a simple CRUD application after all.

So everything works, but the guy who gave him this job refused to pay. He stalled and then just stopped answering the phone. Jack is now furious. So what he does, is publish the databases online, so everyone could see the income of every citizen. Authorities are in panic. They send the police to his door. They seize his computer and lock him up for a few days.

To sum it all up: Jack took up a job, without any contract, without any NDA, which is completely illegal in of itself, but he did that with the tax authority. And delivered the product before getting paid. And when he understood that he was owned, he published all online. He got bit back. The guy who gave him this job had no consequences for illegally hiring someone and not paying for their work.

Lesson: Don't be Jack

Hi everyone, long time no see.

Today I want to tell you a story about Linux, and its acceptance on the desktop.

Long ago I found myself a girlfriend, a wonderful woman who is an engineer too but who couldn't be further from CS. For those in the know, she absolutely despises architects. She doesn't know the size units of computers, i.e. the multiples of the byte. Breaks cables on the regular, and so on. For all intents and purposes, she's a user. She has written some code for a college project before, but she is by no means a developer.

She has seen me using Linux quite passionately for the last year or so, and a few weeks ago she got so fed up with how Windows refused to work on both her computers (on one of them literally failing to run exe's, go figure), that she allowed me to reinstall both systems, with one of them being dualbooted Windows 10 + Linux.

The computer that runs Linux is not one she uses very often, but for gaming (The Sims) it's her platform to go. On it I installed Debian KDE, for the following reasons:
- It had to be stable as I didn't want another box to maintain.
- It had to be pretty OOTB, as first impressions are crucial.
- It had to be easy to use, given her skill level.
- It had to have a GUI abstraction to apt, the KDE team built Discover which looks gorgeous.

She had the following things to say about Linux, when she went to download The Sims from a torrent (I installed qBittorrent for her iirc).

"Linux is better, there's no need to download anything"
"Still figuring things out, but I'm liking it"
"I'm scared of using Windows again, it's so laggy"
"Linux works fine, I'm becoming a Linux user"

Which you can imagine, it filled me with pride. We've done it boys. We've built a superior system that even regular users can use, if the system is set up to be user-friendly.

There are a few gripes I still have, and pitfalls I want to address. There's still too many options, users can drown in the sheer amount of distro's to choose from. For us that's extremely important but they need to have a guide there. However, don't do remote administration for them! That's even worse than Microsoft's tracking! Whenever you install Linux on someone else's computer, don't be all about efficiency, they are coming from Windows and just want it to be easy to use. I use Mate myself, but it is not the thing I would recommend to others. In other words, put your own preferences aside in favor of objective usability. You're trying to sell people on a product, not to impose your own point of view. Dualboot with Windows is fine, gaming still sucks on Linux for the most part. Lots of people don't have their games on Steam. CAD software and such is still nonexistent (OpenSCAD is very interesting but don't tell me it's user-friendly). People are familiar with Windows. If you were to be swimming for the first time in the deep water, would you go without aids? I don't think so.

So, Linux can be shown and be actually usable by regular people. Just pitch it in the right way.

!dev

Just went to the pet asylum to look for a cat. There was a shy black one (eh, maybe not a good first but Moar Blacker, Moar Better 😋) and a black and white one which was very open towards me.

Probably I'll get the latter, and build some food, water and litter dispenser systems for it with motors and my esp8266 boards 🙂

The lady who was volunteering there and showed me around had an interesting story though.

Apparently both of those aforementioned cats were wild cats (so they don't come from a proper household or anything). Except that black and white one which apparently came from some rather retarded people.. think average Facebook user.

According to her those previous owners came there with 2 cats including the black and white one as "extremely wild, we found them in the forest, put them in cages (because everyone carries cat cages in their car every day, right?) and brought them here". Nice excuse for average Facebook user level of retard I have to say 😜 but it's not very waterproof, you know?

But on average the people that they get there are even worse than that.. some get a great initial meeting with a cat, but then leave them there because they don't like the stripes on a paw or something stupid like that. As she put it: "you're not fitting pants in a clothing shop, are you?! 😑"
Had to try hard to not burst out in laughter from that description 😂

Point is, the average customers there are awful.. apparently she was very grateful to have a rather down-to-earth customer like me and my home supervisor (who helpfully drove me there 🙂) for once. So terrible clients.. they're everywhere!

It really taught me to be mindful of the hardships of people in any profession who deal with clients.

I love it when a fellow "dev" asks about some interesting security topic (full disk encryption) and I'm like "yeah I use LUKS pretty much everywhere".. and then takes an entire arm when given a hand.

Performance in LUKS? Yeah sure you can benchmark it within cryptsetup. Here's how to do it and choose a good cipher for your CPU.

D: Oh also how do I check my battery life?
M (thinking): you lazy fucking piece of shit.
M: FUCKING GOOGLE IT
D: Obviously that means that you don't know it.
M (thinking): so not only lazy but also disgustingly ungrateful, fucking twat.
M: acpi. Next time fucking Google it.
D: You know what? Never mind.

As if I'm the one that's fucking wrong now!! But you know what, never mind indeed. Because you've successfully wasted my fucking time instead of fucking googling "check battery life Linux" like a sensible dev would.

Fellow "dev", if you're on devRant I hope you read this. You can seriously go fuck yourself.

Less rant, more mildly interesting Java trivia.

Integer i0 = 3; Integer i1 = 3;
Integer i2 = 300; Integer i3 = 300;

i0 == i1 is true as expected
i2 == i3 is actually false

Java caches -128 to 127 Integer objects for faster perf so when you're inside that range, the objects are indeed the same, but because == checks object equality, the Integer outside of the range is not cached and had to be initialized, so i2 and i3 are two different objects.

You can totally break some tests this way :)

Cracking old recovery CDs for the 9x/2000/XP era shines some light into how companies operated and when concepts came to be in that time:

Packard Bell: An EXE checks that you're running on a Packard Bell machine and reboots if it's not. How do we bypass it? Easy: just fucking delete it. The files to reinstall Windows from scratch come from...
...
C:?
Yup. Turns out Packard Bell was doing the recovery partition thing all the way back to the 9x era, maybe even further. Files aren't even on the restore disc so if your partition table got fucked (pretty common because malware and disk corruption) you were totally fucked and needed to repurchase Windows. (My dad, at the time, only charged at-cost OEM prices for a replacement retail copy. He knew it was dumb so he never sold PB machines.)

Compaq:
Computer check? Nope, remove one line from a BATCH file and it's gone.

Six archives, named "WINA.ZIP" through "WINF.ZIP" (plus one or two extras for OEM software) hold Windows. Problematic? Well... only because they never put the password anywhere so the installer can't install them. (Some interesting on-disc technician-only utils, though!)

Dell:
If not a Dell machine, lock up. Cause? CONFIG.SYS driver masquerading as OAK (the common CD driver) doing the check, then chainloading the real OAK driver. Simple fix: replace the fake driver with the real one.

Issues?

Would I mention this one if there weren't?

Disc is mounted on N:. Subdirectories work, but doing anything in them (a DIR, trying to execute something, trying to view shit in EDIT.COM) kicked you back to the disc root.

Installer couldn't find machine manifest in the MAP folder (it wanted your PC's serial before it'd let you install, to make sure you have the correct recovery disc) so it asked for 12-digit alphanumeric serial. The defined serials in the manifest were something like "02884902-01" or similar (8-2, all numbers) and it couldn't read the file so it couldn't show the right format, nor check for the right type.

Bypassing that issue, trying to do the ACTUAL install process caused nothing to happen... as all BATCHes for install think the CD should be on X:.

Welp.

well that was fun. Now to test on-real-PC behavior, as VBOX and VMWare both don't like the special hardware shit it tries to use. (Why does a textmode GUI need GPU acceleration, COMPAQ?????)

Absolutely not dev-related.

Blah, blah, weird conversation and shit. I'm too tired and lazy to write this crap again, but let's do it.

The guy is a dev I randomly found on some chatting service, he was interesting to talk with until this conversation. I'll write this out of memory, so yeah.

Him: So by the way I wrote an app that you give your penis size to to get measurements and stuff about it.
Me, thinking it was dev humor: That's hilarious. Tell me more, I'm interested.
Him: So the idea behind all of this was to gather some big data style info about people's penis size and habits and all that stuff.
Me: Man that's awesome. Can I see the source?
Him: No, it's proprietary. You can buy a license though.
Me: You went that far for a joke?
Him: What joke?
Me: The whole software you just told me about.
Him: That's not a joke, I'm being very serious about it.
Me: Oh well. What did you get from the stats?
Him: I got some tips from people's habits! I never thought that shaving it could make it look bigger, but that's awesome!
Me: Do you really care about it that much?
Him: Studies have proven that size correlated with confidence. Since I started doing it, I've been more confident than ever!
Me: Great.
Him: I'm a bit disappointed to see that I'm in the lower percentiles though.
Me: Well of course you are.
Him: Why would you say that?
Me: Well since people with a big dick tend to go more willingly into the subject and might even buy a fucking app for it, of course you'd have the higher average in your stats.
Him: You're only saying that because you have a small cock.
Me: Why the fuck would you say that? You're the one that's concerned about it, not me.
Him: Go on, what's your size?
Me, because I don't care about discussing that stuff: *Tells him*
Him: [stats, comparisons and stuff]
Me: Well I never gave a fuck and your stats won't make me change my mind.
[ ... Some other shit about my size compared to his ... ]
Him: Would you want to work with me for the database maintenance?
Me: You must be joking?
Him: I'm serious.
Me: *Deletes account*

Seriously, fuck that guy. I rewrote that quickly so you only had the best, but it was a whole fucking conversation.

I really dislike the company I work at.

I want to say hate, but there are parts that I adore (mostly the people I get to work with).

However, I dislike:
- The management
- The way engineers are treated
- Lack of responsibility for on QA for finding bugs, and it falling solely onto the engineers
- Sales circle jerk every All Hands meeting
- The amount of "ring-around-the-rosy" they played with me for a 10k raise (took 12+ months and not what I was looking for when I first asked)
- They lie

Just a shitty company overall. Interesting product depending on what team you're on, but overall I'd rather dye my hair green and become a talking broccoli stock.

Hey ranters!

I'm here to ask a huge favor.
So I used to be on the app more frequently last year, but I started to work on a shit ton of personal/professional projects. I'm not technically back to being a regular again (probably never will be), I'm back to ask all you great devs to possibly check out a platform I'm working on. It's not 100% completed yet, but I'm at that weird 90% mark where you're almost done but you start to find other interesting things to do, so I'm forcing myself to ask people to hop on it to give me that push. It's going to have some interesting (if I say so myself) features.Definitely appreciate it! (Please don't kill me over the UI/UX, I'm primarily a backend dev...but it'll definitely improve by 100% Launch)

AND ONE LAST THING....I don't have a good name for it yet so..there's that..

THANKS!

This is a long post and if someone comments without reading carefully I don't care about that person's opinion.

I have 3 accounts here, and that is a must have for me. Let me explain:

Let's think of people and who they are in layers.

The innermost layers are made of private and intimate things: fears, dreams, shames, basically things that are mostly shared with very close people, like family, best friends, and specially significant others.

On the other hand, outermost layers are the public persona, who you are as a citizen, who you are in your profesion, and so on.

So, you wouldn't normally tell your boss about your favorite sex positions.

Let's also say there can be layers in the middle, and all the layers sometimes overlap, but let's not get too deep into this as I think I got the point across.

Here on I explain the original thesis.

I am a developer, and as such I want to fulfill my needs on dev communities, one of them being devrant.
I wish to learn from other devs, I expose my (sometimes controversial) points of view. I rant about annoying shit in the workplace.

But also, at some level, I wish to be taken seriously as a developer, I wish to build a reputation, and I wish to be accepted, even in a shallow social level. There is a social factor to what we do and it's totally normal.

Now, the problem is that I also would want to express my inner self.

So what I do is I don't use my main account for that, I use another, in fact 2 other accounts.

There are several reasons for that:

* I want to hide intimate shit from trolls.

Imagine I griefpost about a loved one that died, then later found myself in a heated discussion about some language, and then some troll comments something like "I'm glad your x died". i wouldn't react very well.

* I want to keep my posts consistent.

If people become interested in what I post as a dev, then they are going to expect dev related stuff from me. If I start posting like controversial points of view, that's not very cool because I'd be doing like a bait n switch on them.

* I want to maintain a reputation, and I want to not get banned on the main account

Reputation as a profesional is a real thing, and it shouldn't be affected by your personal shit.
Also sometimes you argue, and things get heated, and sometimes you get suspended or banned.

You try your hardest to be respectful, but in some communities, some mods are trigger happy.

By restricting this on your alt account, you're in a way promising that you'll have the upmost behaviour on your dev account because that means being professional.

Now, I said I had 2 other accounts.

The reason for having 2 is because I separate two layers:

In the 2nd account I am open and direct regarding my points of view, and more argumentative, but still trying to be relatively civil. I would also post things that might be controversial or not popular. I try to be real basically.

You can conclude that the 2nd account is the one posting this, since this post could trigger some people.

In the 3rd account, I talk about intimate shit like traumas, fears, emotional pain, things I know I'll get support for (the same support I give others when in need) and are not controversial in any way.
This way I can vent painful things and avoid trolls.

Cool people appreciate it when you're transparent about your shortcoming and dark thoughts.

But it takes one asshole in a high horse to judge you. And sometimes you need to give that asshole the middle finger without being afraid of ruining your reputation
or getting banned,
or being scared of that asshole laughing about your intimate shit (again, I use this account for that)

I know it sounds like I have multiple personalities but I swear I'm ok, and hopefully what I said makes sense. People might say "don't use alt accounts, go to another site", but I find that devrant has some interesting people.

The obvious downside is that you end up knowing people more than what they assume, because you interact with them through different accounts.

This is kinda shady, but I'm not interested in taking advantage of others anyway so...

It's been two months since I've left my previous job, after 1.5 years. I never had the feeling my boss trusted his dev team, since he was checking up on us regularly, even though we had planned out a sprint and work for us was "clear". I say "clear", because every single feature on this project was pretty much half-baked, since they were just ideas our boss/PO (same person) on the spot and were labeled as "the next big thing" without every properly writing them out as user stories. Every demo came with a bunch of criticism, because features weren't implemented "as he imagined", because what do you know, the user stories weren't properly described anyway. Bringing that up as counter-argument also made him angry every time, so that didn't help much either. The launch of the platform was also postponed every time because of vague reasons, so that didn't make the project any more interesting either.
It took a while before I got sick of this of this pretty hopeless situation and toxic environment. Mind you, it was my first job since I graduated, so I was a bit naive thinking the working environment would improve and aforementioned company issues would be resolved over time. Eventually, I ran out of patience and motivation, so I finally bit the bullet and handed in my resignation letter.
From that moment, I at least had an end in sight, since I was still obliged to do my four-week notice period, which felt like an eternity. The borderline childish and sociopathic behaviour of my boss didn't make it any better (e.g. checking up on me even more, more mistrust, randomly accusing me of ruining the working atmosphere because I shared a meme with a colleague of mine and didn't involve him, going lunching with all of my colleagues but explicitly asking me to stay at work, ...). Being forced to work from home the last 2 weeks as part of the country's lockdown measures at least helped my sanity a bit, since I had the comfort of my home office and not the frequent "looking over your shoulders to check if you're still working".
By the last day of my notice period, I was bitter, exhausted, lost confidence in my skills and had completely lost my joy of being a developer. I had to physically meet with my boss one more time to hand in the company laptop. He thanked me for my service and said that we'd keep in touch. I hope I won't keep that promise (he made a lot of false promises before, too), because I'd rather never encounter him ever again. It felt like a huge relief to finally close the door of this bad experience behind me for good.

Now, 2 months later, I've got a new job and rediscovered my joy for coding, mostly thanks to the complete opposite of a toxic environment here, management which actually has respect and faith in me and a challenging but fun project. My mental state has made a complete turnaround compared to two months ago. I have absolutely no regrets of switching jobs. If only I had made that decision sooner.

I don't like when

you have a couple of years of experience with some language and you're like "I should read a good book about it, and have some proper solid foundation instead of playing by ear".

So you get a book and what follows is a very jarring experience.

Because for the first 8 chapters they get into the basics of the language.

You're occasionally like "interesting, I did not know that".

But for the most part you're like "yes, for fucking christ I know that, everybody knows that",

or you complain about the author being redundant,

or about the outdatedness of the book, since most documentation is now in the interwebs

or you reach flawed conclusions out of frustration like "this isn't making me any money, I could get on upwork, or do some bounties instead of wasting time on this"

then you start to skim through the pages like "I know this, and this, and this" until you realize you're in some page you have no fucking idea what it's talking about, as if you ended up on the wrong side of town

so you start backtracking (frustration is going critical at this point)

but backtracking is annoying because it's not well defined where you stopped getting it, as if in page 33 you were getting it 100%, but 0% on page 34, it's more like a gradual, irregular decrease,

so you have no idea where to start re reading from.

you just shove that shit into the wall at that point.

Some of these are learning discipline problems.

I guess there are ways to mitigate them, such as writing down questions of things not understood, co reading, etc.

But the one thing I don't think I can't get past is when authors write like shit,

like being redundant, using different words to say the same shit

or using confusing sentences that can mean different things at the same time,

or using the incorrect terminology, eg: if I were teaching OOP, saying shit like "classes create objects" but later on saying something like "classes create instances".
They usually nail the definitions the first time, but then use different terms for the same thing. It's shit.

And I think that's a writing culture that I hate.
From school you are taught to bot repeat words.

To say the same shit in different ways.

To be descritive, but vague.

That's absolutely shitty for programming in my opinion.

I Have always wanted to create a game with tons of openness. Kind of a mix between Dishonored, Thief, and We Happy Few. You have an entire active city where people actually have goals and daily jobs and such. It would be cool to have everything time based, so stuff happens even if you're not doing anything, and even be able to live a practically normal life, get a job, make friends. See news happen, and perhaps in the dead of night you turn into an assassin and prevent events from happening that could kill many people. And so on. Just being able to watch the city lively at work and NPCs actually having goals to complete each day, it would be so interesting. I suppose Skyrim is the closest game to my idea as of current

Headsup: if you're making a game, or want to, a good starting point is to ask a single question.
How do I want this game to feel?

A lot of people who make games get into it because they play and they say I wish this or that feature were different. Or they imagine new mechanics, or new story, or new aesthetics. These are all interesting approaches to explore.

If you're familiar with a lot of games, and why and how their designs work, starting with game
feel is great. It gives you a palette of ideas to riff on, without knowing exactly why it works, using your gut as you go. In fact a lot of designers who made great games used this approach, creating the basic form, and basically flew-blind, using the testing process to 'find the fun'.

But what if, instead of focusing on what emotions a game or mechanic evokes, we ask:
How does this system or mechanic alter the
*players behaviors*? What behaviors
*invoke* a given emotion?

And from there you can start to see the thread that connects emotion, and behavior.

In *Alien: Isolation*, the alien 'hunts' for the player, and is invulnerable. Besides its menacing look, and the dense atmosphere, its invincibility
has a powerful effect on the player. The player is prone to fear and running.

By looking at behavior first, w/ just this one game, and listing the emotions and behaviors
in pairs "Fear: Running", for example, you can start to work backwards to the systems and *conditions* that created that emotion.

In fact, by breaking designs down in this manner, it becomes easy to find parallels, and create
these emotions in games that are typically outside the given genre.

For example, if you wanted to make a game about vietnam (hold the overuse of 'fortunate son') how might we approach this?

One description might be: Play as a soldier or an insurgent during the harsh jungle warfare of vietnam. Set ambushes, scout through dense and snake infested underbrush. Identify enemy armaments to outfit your raids, and take the fight to them.

Mechanics might include

1. crawl through underbrush paths, with events to stab poisonous snacks, brush away spiders or centipedes, like the spiders in metro, hold your breathe as armed enemy units march by, etc.

2. learn to use enfilade and time your attacks.

3. run and gun chases. An ambush happens catching you off guard, you are immediately tossed behind cover, and an NPC says "we can stay and fight but we're out numbered, we should run." and the system plots out how the NPCs hem you in to direct you toward a series of
retreats and nearest cover (because its not supposed to be a battle, but a chase, so we want the player to run). Maybe it uses these NPC ambushes to occasionally push the player to interesting map objectives/locations, who knows.

4. The scouting system from State of Decay. you get a certain amount of time before you risk being 'spotted', and have to climb to the top of say, a building, or a tower, and prioritize which objects in the enemy camp to identity: trucks, anti-air, heavy guns, rockets, troop formations, carriers, comms stations, etc. And that determines what is available to 'call in' as support on the mission.

And all of this, b/c you're focusing on the player behaviors that you want, leads to the *emotions* or feelings you want the player to experience.

Point is, when you focus on the activities you want the player to *do* its a more reliable way of determining what the player will *feel*, the 'role' they'll take on, which is exactly what any good designer should want.

If we return back to Alien: Isolation, even though its a survival horror game, can we find parallels outside that genre? Well The Last of Us for one.

How so? Well TLOU is a survival third-person shooter, not a horror game, and it shows. Theres
not the omnipresent feeling of being overpowered. The player does use stealth, but mostly it's because it serves the player's main role: a hardened survivor whos a capable killer, struggling through a crapsack world. The similarity though comes in with the boss battles against the infected.

The enemy in these fights is almost unstoppable, they're a tank, and the devs have the player running from them just to survive. Many players cant help but feel a little panic as they run for their lives, especially with the superbly designed custom death scenes for joel. The point is, mechanics are more of a means to an end, and if games are paintings, and mechanics are the brushes, player behavior is the individual strokes and player emotion is the color. And by examining TLOU in this way, it becomes obvious that while its a third person survival shooter, the boss fights are *overtones* of Alien: Isolation.

And we can draw that comparison because like bach, who was deaf, and focused on the keys and not the sound, we're focused on player behavior and not strictly emotions.

heres something interesting:
The golden ratio is 1.618...

If you're not familiar with it, doing 1/goldenratio
the result is 0.618...
It gives you back the float component exactly.

Discovered that it is actually part of a series.

First of all:
2-(((5-sqrt(5))/2)-1) =
1.618033988749895 -> thats our golden ratio

In other words:
(2%gold) =
0.381966011250106

While:
((5-sqrt(5))/2) =
1.381966011250105

Ok, now we're getting somewhere. We can turn these into variables

First of all, lets see if we can get the golden ratio back out:
2-(((5-sqrt(5))/2)-1) = 1.618033988749895

Okay good.

The formula looks something like
j-(((i-sqrt(i))/2)-1)

Where j = (i*2)+1
That means we can easily figure out what j we need from our i value. (i-1)/2 = j

We run it back far enough we get
1-(((3-sqrt(3))/2)-1) =
1.3660254037844386

Thats the golden ratios little brother. Doesn't look anything like it, but it is part of the series.
And I found a boat load of research documents scattered *all* over the net, where this number and others in the series inexplicably crop up in power series, in chemistry, and elsewhere. Just looks like random floats if you don't know better.

We can actually go lower in the series:
0.5-(((2-sqrt(2))/2)-1)
1.2071067811865475

At the lowest positive value for j, we get
0-(((1-sqrt(1))/2)-1) = 1

It's kinda elegant.

I even wrote a little script to do the conversions:
def gr(k):
....i = k
....j = (i-1)/2
....return j-(((i-sqrt(abs(i)))/2)-1)

The dots are so devrant doesn't break pythons formatting.

!dev

Through life, I've heard some people say horror movies are bad, that they promote violence (usually religious people).

Of course I think that's pure bs, but I think I could provide one argument that is hard to deny, so here it goes, although I might go off rails at the end.

I'll preface with this: life itself is violent. Violence, the word, is mostly used to describe immoral inflictions of harm on other beings.

But you can also say that some deaths are violent by themselves too, event those that weren't caused by humans, like a disease or a natural disaster.

This would be the "visual" meaning of the word, "the way it looks", the shock of humans when observing something gruesome/violent.

That described, it's not hard to also think that technological advancements in modern western life has made such observations of violence very unfrequent for people.

And naturally, modern people get accustomed to the lack of these observations. So accustomed that when they happen they become traumatic.

Because of this, people react weirdly to death. One reaction is censoring the topic. Another reaction is trivializing it, as if it doesn't really matter.

Sometimes they can't even accept old people dying at 90, an awfully stupid reaction in my opinion.

Another interesting reaction is personifying diseases as if they were villains ruining lives intentionally.

Or at least that's what it feels until you look at them through a microscope and realize that diseases aren't more evil than bread changing flavour after toasting.

All of these irrationality and cowardice comes from low exposure to violence, and that's where horror movies balance things out.

Some diseases in the real life can put some of the worst horror movies to shame.

The human body itself is pending violence. Why? Because when you die all sort of worms eat your fucking flesh. And sometimes that happens even before you die.

We bury humans because of the diseases corpses transmit, but also because we don't like the spectacle and the aesthetics of the rotting process.

Just picture for a second bad things happening to your body, and if you feel that is making you too uncomfortable, then maybe you got too used to this too.

I think horror movies help us to remember the reality of our inminent and intrinsic violence.

In ancient times, you would live outdoors, stepping on dirt, and be very used to "bad" things happening to humans.

Nowadays, most homes are sterile clean, and it's unlikely to observe violence.

Oh, some family member is pucking blood and dying from something? Send em to a hospital, or an elderly care center. Don't need to witness that!

I understand and accept grief. What I don't understand or accept is the vilification of death, describing it as something wrong that shouldn't happen.

it almost feels like a burden, like you shouldn't die when you're young, that it's an unforgivable thing to happen.

Well thanks, society, you can't even fucking die in peace.

I would love to die (no suicide) in a mildly celebratory way, watching people around me smile. I think that would be a good ending for me.

But no. Most of my relatives would be fucking crying like the chickenshits they are, ruining it for me.

And that scares the shit out me: people usually say the scary part of dying is that they die alone.

Well that's what dying alone would mean to me: watching people cry instead of smiling at me.

When my grandma died at 80, with all the achievements she made, I considered her death a success, also considering how quick it was. And because of that I didn't mourn for too long.

In fact, I don't even consider her dead, and not because of some religious mumbo jumbo. I guess the memories are still alive in me, I don't know.

Some famous chunk of coal said once that he felt people don't believe they're gonna die. And I agree with him.

Another upside of horror movies is that they hurt nobody, which is why you can enjoy it and not get ptsd, unlink watching a snuff film.

I will also be fair and add that this might a be a cultural thing, but deep down desire for survival is a genetic thing could play a big part in this too.

My Data Communication & Computer Networks (DCCN) teacher was the best teacher I've seen.

Teaching can be super hard. You're one against like sixty others who aren't interested in being there. To make that good learning environment, making the subject interesting etc, it not easy. Some justify that, "I can only bring the horse to the water" & proceed to just regurgitate whatever is on the book. Others cross question you & impose punishments - try to make you learn by fear.

But my DCCN teacher - she had the right balance between strictness & humour. So kids took her seriously (did homework, weren't late), yet never feared her - we felt comfortable asking doubts/questions.

She had some good tactics, like asking us to teach certian chapters - that made us learn better. She would revise them in the end also, incase we missed anything.

My best moment with her was when I scored the highest in my internals. She picked up my paper & showed the class - "see? Just two pages & he scored so much". There's was always those students who pump out a lot of stories/essays or whatever that comes to their mind about the topic in question. Lots of teachers just blindly give marks - "oh, s/he wrote this much, so it must be right".

But my DCCN teacher had zero tolerance for garbage. If you're wrong, you're wrong. Some even believe that the number of marks = number of lines you have to write!! Doesn't matter what you write. So, I was super glad when this teacher upped the standards.

## Learning k8s

Interesting. So sometimes k8s network goes down. Apparently it's a pitfall that has been logged with vendor but not yet fixed. If on either of the nodes networking service is restarted (i.e. you connect to VPN, plug in an USB wifi dongle, etc..) -- you will lose the flannel.1 interface. As a result you will NOT be able to use kube-dns (because it's unreachable) not will you access ClusterIPs on other nodes. Deleting flannel and allowing it to restart on control place brings it back to operational.

And yet another note.. If you're making a k8s cluster at home and you are planning to control it via your lappy -- DO NOT set up control plane on your lappy :) If you are away from home you'll have a hard time connecting back to your cluster.
A raspberry pi ir perfectly enough for a control place. And when you are away with your lappy, ssh'ing home and setting up a few iptables DNATs will do the trick

netikras@netikras-xps:~/skriptai/bin$ cat fw_kubeadm
#!/bin/bash

FW_LOCAL_IP=127.0.0.15
FW_PORT=6443
FW_PORT_INTERMED=16443
MASTER_IP=192.168.1.15
MASTER_USER=pi

FW_RULE="OUTPUT -d ${MASTER_IP} -p tcp -j DNAT --to-destination ${FW_LOCAL_IP}"

sudo iptables -t nat -A ${FW_RULE}

ssh home -p 4522 -l netikras -tt \
-L ${FW_LOCAL_IP}:${FW_PORT}:${FW_LOCAL_IP}:${FW_PORT_INTERMED} \
ssh ${MASTER_IP} -l ${MASTER_USER} -tt \
-L ${FW_LOCAL_IP}:${FW_PORT_INTERMED}:${FW_LOCAL_IP}:${FW_PORT} \
/bin/bash
# 'echo "Tunnel is open. Disconnect from this SSH session to close the tunnel and remove NAT rules" ; bash'

sudo iptables -t nat -D ${FW_RULE}

And ofc copy control plane's ~/.kube to your lappy :)

So I recently purchased Ark and I gotta say I can totally recommend single player/ local multi.

It's not exactly stable. And non-dedicated private servers are pretty limited. But it's fun nonetheless. The animals are neat, the landscape is gorgeous, and the base building is interesting and intuitive.

One of the things I don't exactly love about Minecraft is that your shelter doesn't matter much. Build some walls to keep the mobs out and you're good. But Ark is much more hostile. You need to avoid cold, and rain, and heat, and big Dino's that want to bite you and stomp you. So your shelter actually protects you.

Not only that but materials are so easy to get in Minecraft. You can have a full house by the end of your first day, easily. But Ark makes resource collecting difficult. You need some dino companions to hold your stuff because it becomes too heavy for you alone. And it takes days, maybe even in-game weeks to build a suitable house. And you can spend much, much longer making it more than just a wooden box.

Cool game! Definitely in my top 3 right now.

Hey everyone, have you ever had a creative block right when you're up against a tight deadline? It's like your brain just decides to take a vacation at the worst possible time.

I had a project due yesterday and I was feeling pretty confident about it until I sat down to work on it. Suddenly, my mind was blank and I couldn't think of a single idea. I tried everything from taking a break to listening to music, but nothing seemed to work.

Eventually, I resorted to staring at the wall and hoping for some sort of divine inspiration. But all I got was a headache and a growing sense of panic as the deadline drew nearer.

Finally, in a fit of desperation, I started randomly typing words and phrases into my project, hoping that something would stick. And to my surprise, it did! I ended up with a project that was not only finished on time but also creatively interesting.

So, the lesson I learned from this experience is that sometimes you just need to let go of your expectations and dive headfirst into the unknown. Who knows, you might just surprise yourself with what you come up with.

Tech Twitter is a fucking joke, unless you're a somewhat accomplished programmer, wrote something interesting / useful, or at the least have contributed anything meaningful that isn't just a repository with Markdown documents in then I don't want to see your fucking stupid inspirational quotes or words of encouragement with thousands of damn retweets. The circle jerk is frankly just unbearable.

There are plenty of developers that you can learn a lot from and that's great, and I don't want to put new developers down, but you're really not in any position to be giving advice or motivational monologues, you're still new, or worse yet, you've literally just started. Behave yourself.

I'm convinced they're all just LARPers who jerk each other off and shut people down when they have "naughty" opinions. They spend more time writing articles about HTML tags or some aspect of JavaScript you can just get from MDN and get a million fucking applause for it. Maybe you'd be a better programmer if you actually did some programming.

Okay I'm done

Hi devRant. Wanna rant with some shit about my company. First some good parts. I work in company with 600+ employees. It's one of the best companies in my region. They provide you with any kind of sweets(cookies, coffee, tea, etc), any hardware you need for your work (additional monitor, more ram, SSDs, processor, graphics card, whatever), just about everything you need to make your work faster/comfortable. Then, we have regular reviews (every 6 months), which rise salary from $0.75 to $1.5 per hour. (I live in poor country, where $15 per hour makes your more solvent then 70% of people, so having 100-200 bucks increase every half year is quite good rise).
The resulting increase of review depends on how team leader and project manager are satisfied with my work. And here starts the interesting (e.g. the shit comes in).
1) Seniority level in our company applies depending on the salary you have. That't right. It does not depend on your skill. Except the case when you're applying to vacancy. So if you tell that you're senior dev and prove it during interview, you'll have senior's salary. This is fine if you're just want money. But not if you love programming (as me) because of reasons bellow.
2) You don't need to have lots of programming experience to be a team leader. You can even be a junior team leader (but thanks god, on research projects only). You start from leading research projects and than move to billable if the director of research department is satisfied with your leading skills.
As a consequence our seniors are dumb AF. This pieces me off the most. Not all of them. A would say half of them are real pro guys, but the rest suck at programming (as for a senior). They are around junior/middle level.
I can understand if guy has $15 rate but still remains junior dev. That's fine. But hell no, he is treated as a middle, because his rate is $10+ now! And his mind has priority over middles and juniors. Not that junior have lof of good tougths but sometimes they do.
I'm lucky to work yet on small project so I'm the only dev, and so to speak TL for myself. But my colleague has this kind of senior team leader who is dumb AF. They work on ASP.NET Core project, the senior does not even know how to properly write generic constraints in C#. Seriously.
Just look at this shit. Instead of

MyClass<T> where T: class {}

he does this:

abstract class EnsureClass {}
MyClass<T> where T: EnsureClass {}

He writes empty abstract class, forces other classes to inherit it (thus, wasting the ability to inherit some useful class) just to ensure that generic T is a class. What thA FUCK is wrong with you dude?! You're a senior dev and you don't even know the language you're codding in.
And this shit is all over the company. Every monkey that had enough skill just to not be fired and enough patience to work 4-5 years becomes a senior! No-fucking-body cares and reviews your skill increase. The whole review is about department director asking TL and PM question like "how is this guy doing? is he OK or we should fire him?" That's the whole review. If TL does not like you, he can leave bad review and the company will set you on trial. If you confront TL during this period, pack your suitcase. Two cases of such shit I know personally. A good skilled guy could not just find common language with his TL and got fired. And the cherry on top of the case is that thay don't care about the fired dev's mind. They will only listen to reviewer. This is just absurd and just boils me down.
That's all i wanted to say. Thanks for your attention.

So I'm receiving messages from recruiters weekly (no flex intended), half of which are not even close to what my profile describes. And I got really sick of it so sometimes it takes at least a week for me to respond if I decide you're actually worth a reply (looking at you, automated half-assed messages that didn't even notice I know nothing about Javascript).
The thing is that some of the more useful messages are actually quite interesting and match my ambitions and desires quite well. But I like my current job and love the project I'm working on... Am I the only one who wants to stay "loyal" to their employer and their project, at least for as long as the contract is valid?? I really want to be there when delivering the final product and test it myself but it sometimes means declining very interesting job offers.

How do people decide its the right moment you have to leave for a new job if you're satisfied with what you have currently? I'm graciously rejecting interesting offers in the hope that they respect my "loyalty" towards my current project and stay reachable to me when I need them later on (I've already had some that would hit me up after a year asking me how it went and if everything was still okay). Is this something that happens often or am I just lucky with those specific recruiters??

Like yes, I can surely use the money I'd receive from a better job. But I am still learning a lot on my current job and I am positive this kind of job offers will keep coming over the years (and hopefully even more so because I keep getting more experienced). I'm also not the top candidate for some of these offers if I may say so myself, so is it important to take what you can get or is it better to stick to what you're comfortable with?

Consecutive hours: ~24, it was a hackathon and not terribly interesting.

I did however have an exciting new experience this exam period; a 5 day crunch with strictly timed 6 hour sleep breaks, half-hour lunch breaks and the rest entirely populated by work. I live 5 minutes from the CS lab so this pretty much meant 18 hours of coding per day, 90 hours in total.

Think of this the next time you're trying to decide whether to announce that you aren't going to contribute to a group project.