The hardest part of being a programmer wasn't the education, the self-teaching, the sleepless nights or the hours of agony trying to fix a bug that would break a program I'd spend weeks working on.

It's the realization that my family, friends, coworkers...nobody understands at all what I do. They don't know of my failures or my triumphs. I can't talk about it with them and it's becoming more apparent to them that it's taking up more of my life. And in a way it feels like a part of myself has just become, well, alien.

Best way I can describe it is, it's like the "Tears in the Rain" scene from Blade Runner.

I'm stuck, I think. I know I've been shutting out people from my life more and more as I don't want to "deal" with people's issues, but I don't think it's been good. I'm can verify that I'm depressed beyond my normal levels.

It's time for me to make an appointment with a therapist.

Remember that you are loved here, and appreciated. Don't let anyone tell you different.

Stay strong.

Me being a good collegue teaching my friend basic C++ for upcoming exam and trying my best not tore my friend apart.

Crime scene: university's library, today, 1PM.

Me: Create a new class, just type 'class' and hit TAB
Him: I'm trying to but it pastes some code
Me: That's the point of hitting TAB.. now that we are finished, include it in your main file, the one with main entry point
Him: I have no such thing
Me: Look for main function
Him: There's none, what is it called?
Me: ...main
Him: Yeah, what is it called?
Me: ..main, the name is main
Him: I get it, but what is it called?
Me: 'MAIN' FOR GODS SAKE, THE NAME IS 'MAIN' *points towards my code*..
Him: Oh, okay, I get it now
Me: Ok, let's compile
*Error pops on his screen*
Him: You know what, I don't think you can really program.. *closes laptop and walks away*.

FML

This rant is a confession I had to make, for all of you out there having a bad time (or year), this story is for you.

Last year, I joined devRant and after a month, I was hired at a local company as an IT god (just joking but not far from what they expected from me), developer, web admin, printer configurator (of course) and all that in my country it's just called "the tech guy", as some of you may know.

I wasn't in immediate need for a full-time job, I had already started to work as a freelancer then and I was doing pretty good. But, you know how it goes, you can always aim for more and that's what I did.

The workspace was the usual, two rooms, one for us employees and one for the bosses (there were two bosses).

Let me tell you right now. I don't hate people, even if I get mad or irritated, I never feel hatred inside me or the need to think bad of someone. But, one of the two bosses made me discover that feeling of hate.

He had a snake-shaped face (I don't think that was random), and he always laughed at his jokes. He was always shouting at me because he was a nervous person, more than normal. He had a tone in his voice like he knew everything. Early on, after being yelled for no reason a dozen of times, I decided that this was not a place for me.

After just two months of doing everything, from tech support to Photoshop and to building websites with WordPress, I gave my one month's notice, or so I thought. I was confronted by the bosses, one of which was a cousin of mine and he was really ok with me leaving and said that I just had to find a person to replace me which was an easy task. Now, the other boss, the evil one, looked me on the eye and said "you're not going anywhere".

I was frozen like, "I can't stay here". He smiled like a snake he was and said "come on, you got this we are counting on you and we are really satisfied with how you are performing till now". I couldn't shake him, I was already sweating. He was rolling his eyes constantly like saying "ok, you are wasting my time now" and left to go to some basketball practice or something.

So, I was stuck there, I could have caused a scene but as I told you, one of the bosses was a cousin of mine, I couldn't do anything crazy. So, I went along with it. Until the next downfall.

I decided to focus on the job and not mind for the bad boss situation but things went really wrong. After a month, I realised that the previous "tech guy" had left me with around 20 ancient Joomla - version 1.0 websites, bursting with security holes and infested with malware like a swamp. I had never seen anything like it. Everyday the websites would become defaced or the server (VPN) would start sending tons of spam cause of the malware, and going offline at the end. I was feeling hopeless.

And then the personal destruction began. I couldn't sleep, I couldn't eat. I was having panick attacks at the office's bathroom. My girlfriend almost broke up with me because I was acting like an asshole due to my anxiety issues (but in the end she was the one to "bring me back"(man, she is a keeper)) and I hadn't put a smile on my face for months. I was on the brink of depression, if not already there. Everyday I would anxiously check if the server is running because I would be the one to blame, even though I was trying to talk to the boss (the bad one was in charge of the IT department) and tell him about the problem.

And then I snapped. I finally realised that I had hit rock bottom. I said "I can't let this happen to me" and I took a deep breath. I still remember that morning, it was a life-changing moment for me. I decided to bite the bullet and stay for one more month, dealing with the stupid old server and the low intelligence business environment. So, I woke up, kissed my girlfriend (now wife), took the bus and went straight to work, and I went into the boss's office. I lied that I had found another job on another city and I had one month in order to be there on time. He was like, "so you are leaving? Is it that good a job the one you found? And when are you going? And are you sure?", and with no hesitation I just said "yup". He didn't expect it and just said "ok then", just find your replacement and you're good to go. I found the guy that would replace me, informing him of every little detail of what's going on (and I recently found out, that he is currently working for some big company nowadays, I'm really glad for him!).

I was surprised that it went so smoothly, one month later I felt the taste of freedom again, away from all the bullshit. Totally one of the best feelings out there.

I don't want to be cliche, but do believe in yourself people! Things are not what the seem.

With all that said, I want to give my special thanks to devRant for making this platform. I was inactive for some time but I was reading rants and jokes. It helped me to get through all that. I'm back now! Bless you devRant!

I'm glad that I shared this story with all of you, have an awesome day!

A fanfic based on devRant-chan. The character was created by @caramelCase and a drawing by @ichijou.

This is freestyle. I'll think of an image of a scene and go with the flow. I won't remove my fingers from the keyboard and I won't edit or change anything. That's how I come up with my best ideas.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Notes:

B/N = Boss' name (I was too lazy to think of one.)

Anything in between astericks is in italics.
Ex.) *this is in italics.*

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

It was an early January morning when devRant-chan was situated in her desk, typing away on her laptop. She was working on a Python script for her barbaric client when she could've been out with friends. Oddly enough, her Sunday was surged with tranquility.

Normally, Sunday is when her irksome boss barks orders at her on the phone.

"This is wrong!"

"What is this?"

"Change it!"

devRant-chan resented her boss but loved her job. After all, "you can't force yourself to like everyone," was something her elder brother would tell her.

She released a slight chuckle, the one she would only display at the thought of her brother.

Her musings were interrupted when a concerning thought crawled into her mind like an undesirable intruder.

Why hasn't her boss called to complain yet? It's not that she enjoyed his complaining, which she didn't. She simply found it odd, since he's done this every Sunday morning, since she was a junior developer.

Unless he found someone else to complain to? In that case, good riddance!

But still, it wasn't a euphoric feeling to be replaced. She was already accustomed to his Sunday morning calls that it feels almost lonely not to receive them.

She should call him... Just in case some situation—or—problem—has emerged.

She dialed his number, waiting patiently for a reply.

"Hello," said her boss.

"Ah, hello," said devRant-chan. "I called, wondering—"

"You've reached the voicemail of B/N, please leave a message after the beep."

"Damn..." mumbled devRant-chan with a sharp exhale. "I always fall for that."

Why didn't her boss answer the phone? It was odd of him, considering he's always answered her calls.

She was about to dial her coworker when she received an email, which stimulated her attention. The subject of the email read:

*Important. Please read.*

She opened the email. It was her boss. The email read:

*Hello.*

*In case you aren't aware, I had quit my job, due to the stress. I've left the manager in charge. Starting tomorrow, he will be your new boss.*

*-B/N*

Before she could rejoice in excitement, she detected a strange change of voice, emitting from the email. Did her boss really write this?

That's when she spotted something. The word "tomorrow."

Her boss didn't write this.

He would never use words such as "tomorrow," or "today." He would use time instead. If this was her boss, he would say "in 24 hours."

She checked the IP of the email. Oddly enough, it was her boss' IP.

Still, the pieces didn't fit the puzzle. Her boss didn't complain, answer her call, or use his style of speaking in the email.

Something happened to him and she knows it. Whatever it is, has something to do with the manager, and she was determined to figure it out.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This was just a quick random fanfic, and I'm not sure if I'll continue it. As I said, I didn't plan anything, since it's freestyle. I might or might not continue it, so I'll think it over.

The story of Netscape and Internet Explorer really proves the irony of fate! And how life will come back to bite you.

Back in the 90's you had to pay for browsers like Netscape (it was called a navigator but same thing) but after Microsoft released IE for free with your windows copy in 2002 it crushed Netscape and nobody used it anymore (the graph below).

But! Netscape wouldn't give up and before the company died after it made legal accusations against Microsoft and Bill Gates and made them pay for that they did, but Netscape was too far gone and already were falling apart they decided to make a self detonation (I guess that's what they thought being in that tight corner) and they released the code as open source which would later get taken by Mozilla and be the code base for Firefox.

Now look at how much better Firefox is and how nobody uses the shitty IE!

Kind of reminds me of the scene from watchmen where Rorshack was in prison and said the best sentence in the movie "I'm not locked in here with you. You're locked in here WITH ME!"

There was a guy back at uni who, I'd have to say is just manipulative SOB,

I say this because of two situations:
We started uni, first week of programming homework, I helped him out, second week rolls around and this happens:

SOB: hey can you give me the answers to homework for this week?
Me: no but I can explain my idea process, which I then in painstaking detail, break down everything needed to do the homework, I thought maybe he'd understand the process and get the hang of it, he answers me with this
Me: so now that I explained everything did you understand what to do?
SOB: yeah yeah I do now could you give me the answers

But that ain't the only time, nope, at the same time for another class he was part of our team, where we decided to some ambitious project combining 3d printing + an Arduino to make a turret, needless to say my team mates knew nothing of Arduinos or 3d modelling, I did some 3d modelling in my spare time so I handled that other team mates made the Arduino rotate a motor :/ best they could do, SOB does nothing, assessment days rolls around and lecturer goes around the room we show him the turret, the Arduino and proceed to say SOB has done nothing, never contacted us through the last 6 weeks, despite us trying to do so, he begins to complain saying we lied, lecture takes him out of the room because we were starting to make a scene, and he starts crying! The lecturer gives him a B+!

I then hear him one day joking to this guy that he managed to pass Class A by doing nothing and managed to get a higher grade than the rest of his group, at the time he was copying homework from a person for the first programming class because he failed!

Later I hear in my final year he was hanging out with some first years, a friend of mine sees him and says hi, why you hanging with first years, the group of first years look at him and ask how he knows them, and proceeds to question why they were told he was a first year also...

Not only this but I heard despite failing so many papers (heard he was repeating first programming class 3-4 times) he somehow managed to graduate.... I just can't understand why, oh and he has a job too, managed to get one from a guy he knew working in IT he doesn't deserve his bachelor's degree at all!

Most awkward work event/parts story?

There was a girl who worked in customer service, very goth. Un-kept hair, baggy cloths, dark lipstick, etc..etc. At a company holiday party there were several+many people (mostly dudes) asking "Who is that! ... She's HOT!!" etc (you could hear it from various tables), and someone said "That's Stefanie.", then the "Noooo...OMG..."
Apparently she cleaned up nicely (dressed like she was going to a movie premier, very classy). She and a female friend (also attractive, dressed like a million bucks) were sitting close to each together and you could hear more (inappropriate) comments "OMG, are they together!?...that's fucking hot!....".
Mind you, this wasn't a very big venue (and before all of today's woke-ness), I could hear it a few tables away (again, all dudes, customer service and warehouse worker folks), I *know* they could hear it from their table.
It was so bad Stefanie's CS manager talked about in the break room the next day. She wasn't at the holiday party, but the rumors were going wild that day.
<she's in her 60's and I wouldn't want to be on her bad side>
D: "I can't believe they made such a scene. I would have smacked those young men in the face! Stefanie has a boyfriend and Laura is married. They have been best friends since kindergarten, its disgusting what went on. And another thing..."

It was talked about for many years afterward.

TL;DR: Stop using React for EVERYTHING. It's not the end-all solution to every application need.

My team is staffed about 50/50 with tenured devs, and junior devs who have never written a full application and don't understand the specific benefits of different libraries/framworks. As a result, most of these junior devs have jumped on the React train, and they're under the impression that React is the end-all answer to any possible application need. Doesn't matter what type of app is, what kind of data is going to be flowing through the app, data scale, etc. In their eyes, React is always the answer. Now, while I'm not a big fan of React myself, I will say that it does its job when its tasked with a data-heavy application that needs to be refreshed/re-rendered dynamically and frequently (like Facebook.) However, my main gripe is that some people insist on using it for EVERYTHING. They refuse to acknowledge that there can be better library/framework choices (Angular, Vue, or even straight jQuery,) and they refuse to learn any other frameworks. You can hit them with countless technical reasons as to why React isn't a good choice for a particular application, and they'll just spout off the same tidbits from the "ReactJS Makes My Nips Hard 101" handbook: "React is the future," "Component-based web architecture is the future," (I'm not arguing with that last one) "But...JSX bro.," "Facebook and Netflix use it, so that's how you know it's amazing." They'll use React for a simple app, and make it overly-complex, and take months to write something that should have taken them a week. For example, we have one dev who has never used any other frameworks/libraries apart from React, and he used React (via create-react-app) to write what is effectively a single form and a content widget inside of a bootstrap template. It took him 4 MONTHS to write this, and it still isn't fully functioning. The search functionality doesn't really work (in fact, it's just array filtering,) and wont return any results if you search for the first word in an entry. His repo is a mess, filled with a bunch of useless files that were bootstrap'd in via create-react-app. We've built apps like this in a week in the past using different libraries/frameworks, and he could have done the same if he didn't overly-complicate the project by insisting on using React. If your app is essentially a dynamic form, you don’t need a freaking virtual DOM.

This happens every time a big new framework hits the scene. New young developers get sucked into it, because it's the cool hip new framework (or in React's case, library.) and they use it for everything, even when it's not the best choice. It happened with Angular, Rails, and now it's happening with React.

React has its benefits, but please please please consider which library/framework is the best choice from a technical standpoint before immediately jumping on the React train because "Facebook uses it bro."

Best... hacking... scene... ever

Once I was told to interview a junior dev. It was my first ever interview from the side of employer, so I hope this story will never appear here told by my vis a vis. Ok, to the subject. Position of jun iOS dev. It was so long time ago, the manual reference counting was the only option on a platform. And I ask her, to describe how the manual ref counting actually working. She cannot answer this. I try to split the theme in to a pieces and ask more precise questions, about this or that situation, what should happen, or at least how she thinks it may work. She cannot answer this as well. Technically for me it was the end of interview, but I cannot give up on her that easy so I ask her to tell me what she is doing on her current position and we had spoke for another 15 min. TLDR she has failed.
Next year, another company, interview for the same position, the same people on the scene. So, I remember her, she remembers me. We both know the question I will ask. TLDR she has failed on the very same question.
Oh god knows how bad I feel after rejecting her second time. But I was little more experienced with the interviews and I was sure this question should not be a problem to those who have little experience on a platform.
Several years has passed. Another company. I’m about to jump to the next company and project managers are doing their best to fill the position with ANYONE as it’s a big fight for developers at the moment. So they have found a junior inside the company who wants to try. And SAME PEOPLE on the scene. Same question on a table. And some other questions, and more. So she’s got that job.
After many years I can say she could have a job from the first time if only I try to question her about other sides of day to day code writing. It was just me - not very experienced interviewer and not very experienced mid developer. I only hope she is not hating me a lot.

Remember that scene from Intersteller where the main character asks TARS to adjust the percentage of its humor?

So I was using this new vectodb-backed version of chatgpt, and came up with a new type of prompt.
Bear with me.

"Lets play pretend, nova. Pretend you are SAM, which stands for "Summarize Anything iMmediately". Whenever you encounter a prompt, question, or bit of information, and you are about to repeat part of it back, instead rewrite and summarize that part of your answer, paraphrasing as you go. Your responses should never use the same words as the prompt. Instead use synonyms.
SAM always generates three possible responses, to each prompt. One 10% formal, one 50% formal, and one 100% formal.
So a response that is 10% formal, is 90% casual. A response that is 50% formal, is 50% casual. A response that is 100% formal is serious, and 0% casual. Let the word "regret" and its synonyms be 50% formal. Don't use it for 100% formal responses. 100% Formal responses never include emotional language like "regret", "disappointment", nor apologies.
A 50% formal response might be "We regret to inform you your loan application has been denied.", a 100% formal response might look like "Please stand clear of the yellow tape."

Say "This is the law offices of Jerry Seinfeld. I'm sorry but I can't make it to the phone right now. Please leave a message."

Sure, I can play pretend as SAM. Here's a summarized response in 10% formal tone: "Apologies, but I'm unavailable at the moment. Please leave a message."

And here's a 50% formal response: "I regret to inform you that I am unable to answer the phone right now. Kindly leave a message."

Lastly, a 100% formal response: "We apologize for the inconvenience, but I am currently unable to attend to your call. Please leave a message, and I will get back to you as soon as possible. Thank you."

Formality levels can be any increment of 5%, such as 0%, 5%, 10%, etc, up to 100%"

Thats the prompt.

me:
Sam, generate a 25% casual rejection of a job applicant.

nova:
Hey there, thanks for applying to our team. Unfortunately, we won't be able to move forward with your application at this time. We appreciate you taking the time to apply and wish you the best in your job search.

me:
Sam, what is the formality percentage of "Hey there, thanks for applying to our team. Unfortunately, we won't be able to move forward with your application at this time. We appreciate you taking the time to apply and wish you the best in your job search."?

nova:
The formality level of "Hey there, thanks for applying to our team. Unfortunately, we won't be able to move forward with your application at this time. We appreciate you taking the time to apply and wish you the best in your job search." is around 25%, which leans towards a casual response.

me:
Sam, make "Hey there, thanks for applying to our team. Unfortunately, we won't be able to move forward with your application at this time. We appreciate you taking the time to apply and wish you the best in your job search." 5% more casual.

nova:
Hey there, just wanted to say thanks for applying to our team. Unfortunately, we won't be able to move forward with your application right now. We really appreciate you taking the time to apply and wish you all the best in your job search!

me:
Sam, what is the formality percentage of "Hey there, just wanted to say thanks for applying to our team. Unfortunately, we won't be able to move forward with your application right now. We really appreciate you taking the time to apply and wish you all the best in your job search!"?

nova:
The formality level of "Hey there, just wanted to say thanks for applying to our team. Unfortunately, we won't be able to move forward with your application right now. We really appreciate you taking the time to apply and wish you all the best in your job search!" is around 20%, which leans towards a more casual tone.

* * * * *

You can actually go back and see it.

Heres the original output, 25% formality:
"Hey there, thanks for applying to our team. Unfortunately, we won't be able to move forward with your application at this time. We appreciate you taking the time to apply and wish you the best in your job search."

Heres the one thats 5% more casual:
"Hey there, just wanted to say thanks for applying to our team. Unfortunately, we won't be able to move forward with your application right now. We really appreciate you taking the time to apply and wish you all the best in your job search!"

If you look at the differences, the output version adds five words, subtracts three words, for a total of two words gained.

The original sentence has 39 words.

2/39 = 0.05

The sentence length actually grew an equal percentage to the informalness.
It grew linearly to the difference of the length of the more casual version
versus the more formal version, divided by the length of the original.

Writing code and then testing whether it works... This was pretty badass, until it wasn't.

(Spoilers about Ready Player one here)

FUCK YEAH!
I watched Ready Player One in 4DX AND IT COSTED AN UNHOLY FUCKING AMOUNT OF MONEY!
yet it was THE BEST MOVIE Ive ever watched, AND I MEAN IT! IT WAS SO FUCKING GREAT! THE CGI THE ACTORS!
STEVEN DID AN EXCELLENT JOB!
and as a Trekkie I LOVED the scene of Hallidays death I mean his coffin WAS A FUCKING PHOTON TORPEDO! and in the Last scene you could see a bat'leth HOW HOW COOL WAS THAT!
And dont get me started on all the other References like the Holy Handgranade, Rubiks Cube, FUCKING BATMAN HELPING SOMEONE CLIMBING, Minecraft OASIS edition, Halo... I CANT ITS TOO MUCH!

TL;DR: Computers and I go way back, but I don't know how I ended up as a dev - and am still not certain that's what I want to do for the rest of my life.

Rewind to the early 80's. My friends at the time got the Comodore 64 one after the other. I never got one. Heck, we didn't even have a color TV back then. Only a 12/14" small B&W TV. It's easy to conclude that I spent a lot of time at my friends'.

Back then it mostly was about the games. And, living in the rural countryside, the only way to aquire games was to pirate them. Pirating was big. Cassette tape swapping and floppy disk swapping was a big deal, and gamers contacted eachother via classifieds sections in newspapers and magazines. It was crazy.

Anyways. The thing about pirated games back then is that they often got a cracktro, trainer, intro or whatever you want to call them - made by the people who pirated the game. And I found them awesome. Sinus scrollers, 3D text, cool SID-tunes and whatnot. I was hooked.

My best friend and I eventually got tired of just gaming. We found Shoot'Em-Up Construction Kit, which was an easy point-and-click way to create our first little game. We looked into BASIC a bit. And we found a book at the library about C64 programming. It contained source code to create your own assembler, so we started on that. I never completed it, but my friend did.

Fast forward through some epic failure using an Amstrad CPC, an old 486 and hello mid 90's. My first Pentium, my first modem and hello Internet! I instantly fell in love with the Internet and the web. I was still in school, and had planned to enter the creative advertising business. Little did I know about the impact the web would have on the world.

I coded web pages for fun for some years. My first job was as a multimedia designer, and I eventually had to learn Lingo (Macromedia Director, anyone?) And Actionscript.

Now I haven't touched Flash for about 7 years. My experience has evolved back to pure web development. I'm not sure if that's where I will be in the future. I've learned that I certainly don't know how to do everything I want to do - but I have aquired the mindset to identify the tasks and find solutions to the problem.

I never had any affiliation with the pirate scene or the demo scene. But I still get a little tingling whenever I see one of those sinus scrollers.

Javascript fatigue. Because the node scene is so new it doesn't have the established isms and methods of best practices so every few months the next best framework or library comes out promising to fix the problems we all face

A very long rant.. but I'm looking to share some experiences, maybe a different perspective.. huge changes at the company.

So my company is starting our microservices journey (we have a 359 retail websites at this moment)

First question was: What to build first?

The first thing we had to do was to decide what we wanted to build as our first microservice. We went looking for a microservice that can be used read only, consumers could easily implement without overhauling production software and is isolated from other processes.

We’ve ended up with building a catalog service as our first microservice. That catalog service provides consumers of the microservice information of our catalog and its most essential information about items in the catalog.

By starting with building the catalog service the team could focus on building the microservice without any time pressure. The initial functionalities of the catalog service were being created to replace existing functionality which were working fine.

Because we choose such an isolated functionality we were able to introduce the new catalog service into production step by step. Instead of replacing the search functionality of the webshops using a big-bang approach, we choose A/B split testing to measure our changes and gradually increase the load of the microservice.

Next step: Choosing a datastore

The search engine that was in production when we started this project was making user of Solr. Due to the use of Lucene it was performing very well as a search engine, but from engineering perspective it lacked some functionalities. It came short if you wanted to run it in a cluster environment, configuring it was hard and not user friendly and last but not least, development of Solr seemed to be grinded to a halt.

Elasticsearch started entering the scene as a competitor for Solr and brought interesting features. Still using Lucene, which we were happy with, it was build with clustering in mind and being provided out of the box. Managing Elasticsearch was easy since there are REST APIs for configuration and as a fallback there are YAML configurations available.

We decided to use Elasticsearch since it provides us the strengths and capabilities of Lucene with the added joy of easy configuration, clustering and a lively community driving the project.

Even bigger challenge? Which programming language will we use

The team responsible for developing this first microservice consists out of a group web developers. So when looking for a programming language for the microservice, we went searching for a language close to their hearts and expertise. At that time a typical web developer at least had knowledge of PHP and Javascript.

What we’ve noticed during researching various languages is that almost all actions done by the catalog service will boil down to the following paradigm:

- Execute a HTTP call to fetch some JSON

- Transform JSON to a desired output

- Respond with the transformed JSON

Actions that easily can be done in a parallel and asynchronous manner and mainly consists out of transforming JSON from the source to a desired output. The programming language used for the catalog service should hold strong qualifications for those kind of actions.

Another thing to notice is that some functionalities that will be built using the catalog service will result into a high level of concurrent requests. For example the type-ahead functionality will trigger several requests to the catalog service per usage of a user.

To us, PHP and .NET at that time weren’t sufficient enough to us for building the catalog service based on the requirements we’ve set. Eventually we’ve decided to use Node.js which is better suited for the things we are looking for as described earlier. Node.js provides a non-blocking I/O model and being event driven helps us developing a high performance microservice.

The leap to start programming Node.js is relatively small since it basically is Javascript. A language that is familiar for the developers around that time. While Node.js is displaying some new concepts it is relatively easy for a developer to start using it.

The beauty of microservices and the isolation it provides, is that you can choose the best tool for that particular microservice. Not all microservices will be developed using Node.js and Elasticsearch. All kinds of combinations might arise and this is what makes the microservices architecture so flexible.

Even when Node.js or Elasticsearch turns out to be a bad choice for the catalog service it is relatively easy to switch that choice for magic ‘X’ or component ‘Z’. By focussing on creating a solid API the components that are driving that API don’t matter that much. It should do what you ask of it and when it is lacking you just replace it.

Many more headaches to come later this year ;)

A colleague of mine were bashing all day long about which JavaFX scene builder is the best. Let's settle this what do you think?

It annoys me immensely when I struggle with myself, criticizing my own lack of knowledge in certain areas and my colleagues say: "You'll learn by doing". No, I won't, that's a foolish dogma.

I won't and I have never learned by 'doing'. The best results I've obtained have been through understanding every last bit of what's under the hood of a particular functionality. I'm not going to understand the white box by constantly probing the black box, it's just unsatisfactory and insufficient information. It's even dangerous to base yourself on the black box results because you often might get false positives.

I got through university by massive multilateral sensory focus: kinesthetic (writing things down), auditory (listening to the professor), visual (observing graphs and models of the material taught), conscious (mentalizing it all and interlinking information so that later it's accessible from long-term memory). I can confirm this is necessary for the brain because a Neurologist once told me just that.

At least for me, I had the most horrible grades (D's and F's) in freshman year with the 'learn by doing' method and the best grades (A, A+) with the multi-sensory method in later years as I matured my studying methods. In fact, with that method I've continuously outsmarted other people who had 10 years more experience than me ('experts', 'consultants',..) but they preferred to stay in the ignorant 'bro zone' rather than learning things properly. Even worse, the day they arrived on the scene, they completely broke the production environment and messed it up for the whole team. I felt like banging my head on my desk. It just makes me disappointed in the system.

If you follow popular method, you'll soon find yourself in the same problems that arise from doing what everyone else does. What happens at that point? That's right, they have to call in someone who actually bothered learning things.

hey uh, this is a rant about phantom forces, if you don't know what it is, look it up, anyways, that's really it.

so, i've been playing this game very actively called phantom forces and its a good game but its been ruined and the fun has pretty much been taken away. the community is dead and terrible, the developers don't care and the game is just falling off.

what i consider community is the youtube scene, and now as of january 1st, 2022, there's nothing left that's actually interesting besides godstatus and moons fps studio. honestly, its so dry and i'm sick of it.

i'm tired of seeing shitty best setup videos and gun reviews. i hate somesteven and strider and then, there's nothing to actually watch so i just watch brain-numbing shitty videos about stuff.

and then theres the developers, stylis studios is a great development team, i'll give you that but the sheer ignorance of their team is so fucking much.

its kinda obvious they don't really care about adding new features or anything new that isn't guns and its fucking sickening. just to see the same old updates, every fucking month man, its annoying and tiring.

i'm fucking tired of just seeing ape shit guns that are too high for regular players to actually unlock. like i know they're trying to please the growing number of 200+ rank users but its terrible, they haven't done a gun below rank 200 or 100 in forever. the last time they did it was like 6 months ago or something.

we've been asking for shit for years and they haven't given it to us and its fucking tiring. asking for daily quests, new features, more grips, vehicles and shit like that is obviously never gonna happen and thats the fucking problem. they don't care about their community.

but anyways, thats really all i want to say, might make a follow up post later. if you want to add your 2 cents down in the comments, you can do that. bye

Once upon a time in the exciting world of web development, there was a talented yet somewhat clumsy web developer named Emily. Emily had a natural flair for coding and a deep passion for creating innovative websites. But, alas, there was a small caveat—Emily also had a knack for occasional mishaps.

One sunny morning, Emily arrived at the office feeling refreshed and ready to tackle a brand new project. The task at hand involved making some updates to a live website's database. Now, databases were like the brains of websites, storing all the precious information that kept them running smoothly. It was a delicate dance of tables, rows, and columns that demanded utmost care.

Determined to work efficiently, Emily delved headfirst into the project, fueled by a potent blend of coffee and enthusiasm. Fingers danced across the keyboard as lines of code flowed onto the screen like a digital symphony. Everything seemed to be going splendidly until...

Click

With an absentminded flick of the wrist, Emily unintentionally triggered a command that sent shivers down the spines of seasoned developers everywhere: DROP DATABASE production;.

A heavy silence fell over the office as the gravity of the situation dawned upon Emily. In the blink of an eye, the production database, containing all the valuable data of the live website, had been deleted. Panic began to bubble up, but instead of succumbing to despair, Emily's face contorted into a peculiar mix of terror and determination.

"Code red! Database emergency!" Emily exclaimed, wildly waving their arms as colleagues rushed to the scene. The office quickly transformed into a bustling hive of activity, with developers scrambling to find a solution.

Sarah, the leader of the IT team and a cool-headed veteran, stepped forward. She observed the chaos and immediately grasped the severity of the situation. A wry smile tugged at the corners of her mouth.

"Alright, folks, let's turn this catastrophe into a triumph!" Sarah declared, rallying the team around Emily. They formed a circle, with Emily now sporting an eye-catching pink cowboy hat—an eccentric colleague's lucky charm.

With newfound confidence akin to that of a comedic hero, Emily embraced their role and began spouting jokes, puns, and amusing anecdotes. Tension in the room slowly dissipated as the team realized that panicking wouldn't fix the issue.

Meanwhile, Sarah sprang into action, devising a plan to recover the lost database. They set up backup systems, executed data retrieval scripts, and even delved into the realm of advanced programming techniques that could be described as a hint of magic. The team worked tirelessly, fueled by both caffeine and the contagious laughter that filled the air.

As the hours ticked by, the team managed to reconstruct the production database, salvaging nearly all of the lost data. It was a small victory, but a victory nonetheless. And in the end, the mishap transformed into a wellspring of inside jokes and memes that permeated the office.

From that day forward, Emily became known as the "Database Destroyer," a moniker forever etched into the annals of office lore. Yet, what could have been a disastrous event instead became a moment of unity and resilience. The incident served as a reminder that mistakes are inevitable and that the best way to tackle them is with humor and teamwork.

And so, armed with a touch of silliness and an abundance of determination, Emily continued their journey in web development, spreading laughter and code throughout the digital realm.