It shouldn't.

This can apply to webpack and electron apps too

sure. have fun learning 1000 js frameworks

If you want a job and you want it quick, sure. There's some good money in frontend. But in terms of "technology" it's the same bullshit. It's still web development. Overnegineered, bloated software.

You're... YOU'RE THE GUY IN THE VIDEO!!!!

Brendan Tracey I disagree, this exact same thing happened to me 🤣

They say that in the meeting but email the upper manager that everything is on schedule and you get to go in on saturday.

@@flamingspew No they just hardcode the list of user providers but then the next time a new one comes online everything goes down in flames and the on-call has to go in on a Saturday 9 months from now and fix everyone else's mistakes (by just hardcoding a new user provider).

I actually thought that was one of the funniest and most accurate parts.

@@flamingspew And then will only give you a 'meets expectations' at the next Focal, triggering a PIP.

haha one of the best comment! I think I'm not there yet lol

lol true

Bingo knows everyone's name-o, bro.

LMAO

@@rowanreid5457 LMNOP

ISO timestamp support when

Yes(

You either die a wingman or live long enough to become omega star

oooweee

lmfaoooo

That's me when learning anything related to computers in-depth. From processors up to websites, it's all a house of cards where cards on the bottom somehow also rely on cards on the top.

Basically it purely works on human sacrifice.

@@moristar Grace Jones' Corporate Cannibal comes to mind.

😅😂 👌 👍

reincarnation wait retry

ryan Lol!!! So true

At this point, i use tips from the book '100 Tricks to Appear Smart In Meetings' ... to counteract any meeting, just for self amusement :-)

Never seen this much appropriate comment on the post !!!

I´m in the position of the product manager but with the emotions of the engineer

Im a backend developer and i have most definitely seen the drama that is going on here, i have seen it pushing deadline after deadline, i have seen it eating up resources, i have seen it as the reason the design being an absolute hell, i have seen it destroy a (good part of a) company. Quite happy thou i now know the fate of some company's and the people to run from !

Senior Software Engineer

How do you represent the time of the end of the universe in ISO time and perform the conversion faithfully?

@@martir.7653 Yes.

I would sooner lay you into this barren earth than entertain your folly for a moment longer.

Better generalize it.. so that it can convert omegas time to any required time format.. oh yeah, to fetch and maintain list of time formats we might also need a new service 😅😋

The same man. After seeing the insanity of distributed monoliths just a few too many times I've lost all hope.

Higher pay & Better fitness

Yep and actually I did

You don't mean it. A/C is one hell of a drug.

😂😂😂😂😂🤣🤣🤣🤣

*Gordon Ramsey enters the chat*

to cook evryone's favorite spaghetti )

As opposed to those famous medical chefs.

I've been thinking a lot I'd be happier if I'd picked up baking. Then I take a look at my kitchen and yeah, let's not kid ourselves, this is the only thing I know how to do that people will actually pay me for.

@@sacredgeometry yes. “Chef” just means “boss”, it's cognate to “chief”. Chef Doctor is literally a position that exists, it's just rarely called that in English. The cooking association just comes from English people shortening “chef de cuisine” (chief of kitchen) and “sous chef de cuisine” (vice chief of kitchen) to just “chef” (or overhearing french cooks say just chef, because they don't need to specify that they mean the chef cook anymore than a police officer addressing the “chief” needs to specify he's referring to his boss, not a cook)

Lol 😂

😂👍🏻

😃🤣🤣🤣

🤣🤣🤣

Emojis

More like once a week... on a good week. And once a day on bad one...

If you want that button to change colors when you hover over it you’ll have to get the SysKey from my grave!

Lol, exactly

This hits especially harder if you are a front-end dev. People go really crazy with UI requirements.

Unironically when your company wants you to make their app a Skinner Box.

Holy Cow, how is ISO not the first implementation?!! Man, f*** dates!! And idk about that command-structure.. What if ISO is the first.. 🥶😭

Why can’t they use a f****ing UNIX EPOC?

@@eduardoandrescastilloperer4810 they work with time representing end of the universe. unix time is for pussies

@@@eduardoandrescastilloperer4810 Because then they'd need to import the ISO2UNIX framework which is still in beta.

@@eduardoandrescastilloperer4810 Unix epoch time runs out 2038 for 32 bit time stamps, clearly not enough time to for Galactus to know the end of the universe.

Everyone wants a piece of the pie Obama did and he got a big piece.

Thank you AWS!

The reality is, it's really hard to write scalable applications. Especially in an "agile" world, where requirements are constantly changing.

​@@Unknown-jt1joOh, I know, I'm an engineer too. I'm doing that thing called "joking" that they taught us about in college.

What software do you use to count experience years? Omega Star?

Wait a minute, computers only existed for the past 60 or so years...🤔

@@itsasadbunny Not on the astral plane where battles are done...

@@itsasadbunny CLEARLY you don't understand temporal ISO time or you wouldn't ask such a silly question...

Exactly. Every service is either already deprecated, soon-to-be deprecated, or 3 years behind on delivery of the feature some guy promised in a StackOverflow comment was coming soon.

Ahmad Khan Dew it

I’ve emailed this to my entire corporate list

Best one

You have a lead architect! Your organization is full of shits.

@MasterOfDone this is by far my favorite piece of nonadvice for an arbitrary dilemma

Omg checks out 🤣🤣

Great explanation!

Try explaining that to the incompetent Galactus morons!

Spoken like a true omegastar dev. When will you guys wake up to the real world the clients need and get your ISO timestamp shit together!?

@@bransonS look we just can't rely on the BIPM to update our clock with leap seconds that's just impractical and will lead to counterfactual clock scenarios. It's got to be TAI, you can implement a TAI to UTC conversion service at your own peril but otherwise were marking this as CLOSED WONTFIX

Did you change it because of the video because that's awesome!

@@VivekYadav-ds8oz Look I'm not the guy but I'm pretty sure they changed it because of the video.

@@khoavo5758 look I'm not that guy either, but I'm pretty sure they changed it because of the video.

​@@jmanpolo5611 Mira, tampoco soy este flaco pero estoy bastante seguro de que lo cambiaron por el video

@@RHV044 Olha, eu também não sou aquele cara, mas tenho certeza que eles mudaram por causa do vídeo

Exactly! And most businesses that decide to use microservices for that reason never reach a scale where the benefits of microservices offset the costs of having an application that's much harder to maintain than a monolith would be.

​@@Monaleenian Yes but but but THE CLOUD!!!

@@touristtam We all drank the Kool-Aid, that's the truth. But there sure were a lot of people selling the Kool-Aid.

Tech websites: "EDDM is the latest trend in software architecture!"

I dont think you are even allowed to say that.

Just 2 hours? I think you're estimating low.🤣

lubibul If only we could just sunset Ringo2, that thing is a rats nest

@@roeniss yes

Exactly what I was thinking. And I thought only my organisation has these fancy names for services.

@@nikhilkenvetil1594 Doesn't the fact that these services are external to your organization imply that your organization is not the only one with access to them?

@@skepticmoderate5790 You're stating the obvious. How does that matter? And I'm not talking about my organisation having access to aforementioned services. I'm talking about the nomenclature. Kratos, Amethyst, Goldmine, STS etc are names of the serives I've used in my organisation. Fancy names for not-so-fancy serives they provide.

The creator of this video watched the nerds talk during the office time and made it a scene. :D

Well . . .its a nice switch for you hey? After you nerds making just us laugh for so long.😆

_This little maneuver is going to cost us 5 years_

@@theenigma1109 LOL

Yep, 100%, and I love that he fundamentally doesn't understand that it would have the same problem as birthday haha

I've experienced this waaaay too many times. As he gets up, the product manager brings up 3 new requirements and before you have time to react he's gone and you know you're gonna be fucked

Good luck for 2 seconds of delay for each query

Are you the NHS?

Probably fine in 95% of the cases. For the rest: you've grown enough to make use of a DB worthwhile, and learned a lot about your requirements to know how to set up said DB

Just one CSV file, huh? You are not a person to be trifled with.

@@developandplay Hahaha

The camera work on this video is pure gold!

LMAO

"The only solution is to rewrite everything in ..."

Well, this still makes sense. You lose some decoupling by other services having the database service dependency, but each service except that one still has all the benefits of microservices (like using the best technology/tool/language for a specific problem, making changes to it/redeploying etc. without affecting others, separate teams etc.) minus the extreme overhead management of redundant data synchronisation between services. The only time ive ever seen microservices used in practice is exactly that way, the data redundancy across services is totally impractical in most cases. That being said, in some cases you shouldnt use Microservices to begin with...

@@stylishskater92 didn't read, am stuck with a 50,000 endpoint REST API. Help.

Fuck man thank you. Dealing with enterprise java microservices mames me want to nosedive off a mountainside. Why do we need 58 different dependencies when we have direct fucking access to the DB. Just a simple server running sql scripts is so much simpler.

or 19 January 2038 which is the max of 32 bit time.

No you see that’s the bug. The end of the universe time represents he will be alone forever. This is because the EKS chaos server isn’t selecting an acceptable date range so the user aggregate service provider (god) cannot send a girlfriend (user object) to his birthday service (his birthday party) so that his wingman service can hook him up. And in addition the omega service won’t be able to provide a iso date (acceptable partner) before the end of the month. So you’ll need to reduce the entropy of the EKS service by reducing the pool of users (Lowering his standards for mating partners) so the date range is within a month to locate his birthday service (get a date for his birthday). Hopefully it will fix his work priorities and leaving him with more time to code and hit the deadline

Hello Y3K bug... XD

I bet you are a lot of fun at parties.

You know nothing of Galactus' pain.

Put this on your dating profile and find true love.

In what way is "lived experience" different from plain, old "experience"? Lived experience seems like wet water!

Did you resign? I'm having the same experience now and I'm considering leaving.

@@Monaleenian hearing about other peoples lives contributes to our human experience but it’s not part of our own lives experience

And we know there's no point in working on something that's about to be replaced in 5 years.

Either that or it gets deprecated, split up into like 3 other services, and then everyone actually using the service hates the new version because it split up things that were actually used together 3 different services you have to use now. Also of course, at least one of those 3 services is actually another service that's impossible to navigate because it has about 15 different drop downs and may as well be the service graveyard.

Stuart Charlton lol I think thats his meta narrative in the comics to prune planets

Well, technically, one would need Silver Surfer, but that's neither here nor there

Problem is everyone thinks they know what they are doing But they learnt it from a medium post about a deprecated service designed by someone that had no idea what was doing

D You underestimate imposter syndrome

Actually omega star fucked it up. Because they don't provide ISO timestamps. How dare they!

Ok, I just DuckDuckGo'd this and ... I have no words. Is this real life? What day is it? Help

2pts for spec research

haha i can't believe Korean birthdays showed up in this video.. It's not that every Korean's birthday is 1/1 (Koreans still celebrate their own birthdays on different days), it's that every Korean turns a year older on 1/1. This effectively treats everyone born in the same year as a "cohort". This makes it easier to figure out if someone's senior to you or not in social settings as you can simply compare the birth years (seniority is very important in Korean as it determines every aspect of the relationship down to the language you use). So a typical introduction in Korean includes a question about which year a person was born in, and it's not considered rude at all. Another tidbit is that when a Korean baby is born, he/she's considered to be "one" year old. Some people explain it's b/c you count the months in the womb, but it's actually not true (babies are not in the womb for a year anyway). It's actually b/c in Korean, the word for "age" 살 (pronounced 'sal') is ordinal, so when you say a baby is one year old in Korean, it really means it's his/her "first" calendar year of life. There is a cardinal word for age, which is 돌 (pronounced dol), and it means exactly what English speakers would expect, but this is typically only used for babies, or for anniversaries. Now these two facts do cause some peculiar cases. For example, if a baby is born on 12/31 at 11:59 p.m., he/she'd be "two" years old a minute later, and other kids born a minute later would have to use honorifics to him/her. :)

@@yukw777 My mind semi-melted through that, but that was some awesome information you took the time to explain, thank you.

So many easter eggs.

But consider the alternative - working in waterfall... I'd quit IT forever, maybe take up, I don't know, woodworking?

@@plixplux good enough for Jesus...

…until the end of the Universe.

right :D

Haha underrated

We tried this, it worked wonders at first but we encountered massive consistency problems and this crippled our cross-region replication strategy

@@chenseanxy I read that as cross-religion. Is there a microservice for that?

That's just part of the Herald microservice cluster.

damn been a long time since TMP...hope all is well in the pandemic

:(

and then when the original devs have all left the company and the new brains convince the bosses to replace the whole thing, then they work on Galactus 2.0 for a year before quitting because, as it turns out, all of the shiny new tech they're using to build it has bugs and isn't widely supported, and they went about it all wrong from the start. Galactus 1.0, with the weight of the entire company on its shoulders, has not been maintained, and still can't produce the user's birthday.

Because we know the managers. If you burn it to the ground, whatever emerges from the ashes will be only a greater aberration, more pure in its insanity.

It can be both

@@Jbs6187 Depends. Do you work at Twitter ?

Don't worry, we definitely think the latter and that we are collectively to blame.

Yea I got that PTSD, until I took arrow from knee

It's always the last 15 minutes of a multi hour meeting when someone says "Oh! we could do [insert mission impossible here]!" I think the worst is where you have multiple systems that don't have proper APIs, and you're asked to tie them together, and you're forced to do a shit job because what can you do?

yep

Oof. This brings me back so many awful memories xD

That's because it was filmed at Amazon

@@unorigionalHandle yeah I looked him up and he used to work at Amazon, makes sense

Unfortunately, the antithesis to naming a service a "not-stupid-name" means naming it something that it was intended to be, and it gets bastardized over time to do things it wasn't meant to do, which turns it into an incorrectly named service. So which is worse? A service with a name that doesn't describe what it does, or a service with a name that describes something that it no longer does?

Microservices are painful but this video makes it frightening. It's not that deep.

@@barryblack8332 the point isnt the architecture style of microservices - its more a rant of technical debt, flimsy and complex legacy-modern hacks and the hopelessness of explaining to product managers how their previous decisions are creating massive sinks in time to market

@Adrian R I have a Masters degree in Electrical Engineering and am a software Engineer also. Its was difficult to get here. I gave up a lot.

@@steinarst9084 No its both.

@@steinarst9084 this. Microservices as an architecture are insanely powerful, but they must be done right.

all saas is by definition a sisyphean task. for everyone involved, even the users.

I wish I could upvote this more than once

7. The git push --force is a must 8. Oh no 50% salary cut because of complete breakdown

But why don't you just think ahead so you can easily add functionality???? Everytime you change it you just change it a little bit... like spaghetti.

The only way is to rebuild the entire thing from the ground up once a critical mass of unforeseen requirements has been forced on the base that was designed for something else.

They need to implement some real-time dynamic scaling to handle those increased load scenarios. Then utilize machine learning algorithms to spin up nodes just before they're needed to avoid cold start lag.

We'll need to add a few more columns to our AD database to track if a user has a Korean birthday...

Your solution is nice and also what I would do at first but it would cause problems at scale because it would ping database every time user loaded home page (assuming you have a "check out" widget on your navbar. If you have lots of users this could prove very expensive to DB, especially with the inner joins. Ideally you would launch your direct query as MVP first sprint and then follow up with a single caching layer that gets updated periodically. Still, good job on taking initiative and ownership to resolve obvious BS situation.

@@jibreelkeddo7030 Yeah, so these are the tradeoffs. If you need to serve millions of simultaneous users, you need stuff like WINGMAN and BRBDLL to serve the majority of common requests, even though those services don't have all of the knowledge. It's too expensive to have something that knows a lot serving all of the requests. But you still need that stuff, like Galactus, in the background to serve uncommon requests that need more concentrated knowledge. If you only need to serve hundreds or thousands of simultaneous users, then you need a lot less, and you may be able to pull straight from the DB. You might still want to build out more robustness, though, if you think you might hit one of those viral explosions in user count. Like all things in engineering, life is a series of tradeoffs, and there is no single correct answer. The first step, though, is to know what scale you are operating at now, what scale you'll need to operate at in the future, and what you need to do now to even get to the future.

Seems like your backend team got the idea that every action needed to be its own microservice. Outside of Amazon-scale, that's sheer absurdity. The microservices even seem to rely on the same DB tables!

⁠@@jibreelkeddo7030*This* “at-scale” shit is why modern software development is such a bucket of Fail most of the time. “At scale”. Who do you think you are? Google? It’s a shopping cart. For an actual e-commerce business. The numbers of calls to this equals….the number of items that are bought. A modern commodity web server that you can stick under the desk in a broom cupboard should handle easily 20k+ DB queries per second. That’s *Per second*. How many businesses do you think there are sell 20k items *per second*? That’s 70million items per hour. Even in Xmas rush, that’s…..well over a billion dollars revenue per day unless you are selling penny chews. From a single web server. Maybe Amazon sells that, nobody else. “At scale” is the main reason why most software that should run on a single server with CPU cycles to spare is bloated until it *requires* load balancing over multiple data-centres. Fail.

@@creamyhorror probably the backend team leader has no idea how the whole backend infrastructure is connected together. therefore they are building a new road to find all the stuff, or they are just plain lazy

This is an actually simple client request at least it should be. This isn't a case of the PM not knowing anything about the complexities of a problem. This is to do with engineering overcomplicating the problem. I am an engineer btw not a product manager.

Yes. **sobs uncontrollably**

Unity?

iirc the person who made this video works at aws

everybody thinks this is about their own company

@@TheSpacecraftX My exact first thought too.

Otherwise, you'd be out of jobs. Developers are hired to fix the problems they create.

You mean a guy that describes a shitty architecture

@@boot-strapper This is what happens when people start listening to trends, arguments from authority (more and more without any reasonable backing argument) over having a good acumen for engineering (which is unfortunately extremely rare i.e. 1.5% of people at most). There is a lot of needless machoism and postering in software engineering. Significantly more than existed even 10 years ago. People want to experience working on architectures that the "big boys" get to use, often once its up and running they will hate it, move on leaving behind them the mess for other people to suffer with. Then without learning their lesson or demonstrating any sort of self-awareness or introspection move on to the next trend which will "obviously" fix the problems they experienced in their last pet cluster-fuck architecture, design pattern, 5 letter acronym etc. It's tragic. But it's the product of constantly selling the demonstrably obvious lie that anyone can become a software developer for the last 20 years.

@@sacredgeometry agree completely. When I suggest using monoliths for certain projects I get a lot of flak. But honestly you cannot use a hammer for every problem…

@@sacredgeometry dude thats sad. Clusterfuck is the word that I've been looking for the last 2 months since I started working on my current job. The worst part is the techlead is planning on quitting, leaving me as the next techlead, even though I still consider myself a junior/mid level front-end dev, which means he's really desperate to leave behind all the fckin mess he created himself.

@@juliansoto2651 howd it go? 😄

Same here :'D

No, wait long enough. This sketch will then be obsolete as well, and will require deprecation, but not until full adoption of said new sketch

@@jgordon7719 //ignore-rule no deprecation And use it for another five years until 50% of users can't use it anymore.

All other sketches have officially entered maintenance mode.

It's sadly not a sketch. It's a mildly amusing documentary on the current state of software development.