Awkward holiday party story?

Not sure how awkward this is, but our company gives away some fairly nice 'prizes' at the party. Several big screen TVs, KC Royals/St. Louis Cardinals game tickets, etc, etc.

A few years ago, tax laws forces us to charge the employee tax on the items given away at the party (taxed as part of their salary). Awkward part was HR didn't tell anyone until nearly all the prizes were given out.

HRMgr: "Oh, by the way, this year we are forced to include the price of the item as part of your salary so the appropriate taxes are taken out. If you have any questions, come see me on Monday."

I swear I could hear several "WTF"'s from various tables and (to me) awkward silence.

The HR manager sent an apology email to the company saying he should have let everyone know before the party so individuals could make an informed decision about whether or not they wanted to accept the prize.

Seriously?

At the end it's all about being good at excel

Starter pack

Linux Directories cheat sheet ✌️

Pick yours

Sometime I’m developing in Rust and I do something wrong.

Then I look at the terminal and it says...

“You did X, did you mean to do Y”

Then I do it and it works perfectly, and I’m like...

Why do I even have a job if the compiler is this good?

A good thing to share for now :- Artificial Intelligence neural networks !

So, I was gonna rant about how it can be difficult to design event-based Microservices.

I was gonna say some shit about gateways APIs and some other stuff about data aggregation and keeping things idempotent.

I was going to do all this but then as I was stretching out the old ranting fingers I decided to draw a diagram to maybe go along with the rant.

Now I’m not here to really rant about all that Jazz...

I’m here to give you all a first class opportunity to tear apart my architecture!

A few things to note:

Using a gateway API (Kong) to separate the mobile from the desktop.

This traffic is directed through to an in intermediate API. This way the same microservices can provide different data, and even functionality for each device.

Most Microservices currently built in golang.

All services are event based, and all data is built on-the-fly by events generated and handled by each Microservices.

RabbitMQ used as a message broker.

And finally, it is hosted in Google Cloud Platform.

The currently hosted form is built with Microservices but this will be the update version of things.

So, feel free to rip it apart or add anything you think should change.

Also, feel free to tell me to fuck right off if that’s your cup of tea as well.

Peace ✌🏼

A handy linux tutorial for whom cares!