@Lensflare our env variables, networks and docker commands were borked beyond belief for a while now, nobody ever cared to check (they're probably going with the same dockers running for months, never restarting it).

I realized it and fixed it two months ago, but I did so in my own branch (not yet merged in develop) and ofc the junior was unaware of all this; on top of that, his environment had some further problems with missing env variables and the likes.

@BordedDev he's a junior frontend developer and the dockers were entangled beyond recognition; so much so, even I needed the help of a senior devops and 3h to untangle the mess. He gets a pass; the tech lead which was supposed to help him for the previous year, of course, should and will be fed to a wood chipper.

The second junior has been working for the past 6 months with a malfunctioning docker setup. Also cors errors.

We got a long way to go.

UPDATE: as per my own arbitrary decision, every junior is hereby entitled to two whipping sessions every day, at 11am and 4pm. These whipping sessions will have precedence over any other task I have control of.

During these whipping sessions -which might last anywhere between 5s and 50m depending on how stuck they are in the mud- they'll be provided with programming patterns, good practices, fixes for the most obnoxious bugs they are encountering, tips to figure out on their own what should fall within their domain and verbal diarrhea.

Let's go.

@fruitfcker your frontend dev doesnt' know how to work with webpack, .env files and security.

He might be great at everything else, styling and componentizing and what not, but this is a severe issue with the fundamentals and I would immediately rethink letting him work unsupervised on any project.

@BordedDev I'll probably go even further than that and make them do something together.(even then, the former junior is right next to my desk and gets to see everything I do to the new junior). I just need a few days to test the waters, I just don't have any clear idea right now because the situation developed quickly, but tbh I'd be a fool not to make the former junior play some sort of part. He's young... but he's equally talented and hard working; probably even more than I was at that point in my career. I just need to iron out the details a little bit.

I'll elaborate further: if you wanted to have both of these environments aligned without recompilation, you'd have to

- expose your .env to be downloaded on the client side: massive security issue. Cannot overstate how severe would that be

- modify all the code relying on configuration variables: they now come from a server, so you'd need to await everything

- what if you wanted to set your server url in the .env file -which, incidentally, is the first thing you'd want to use it for-? How would the client know the server url to fetch the .env file from? It's on the .env file!

On top of that, the precompilation allows Webpack to recognize unused branches to reduce bundle size (if ALWAYSFALSECUZCOMPILINGFORPROD do THING can be safely removed)

But, then again, all of that is clearly stated in the docs (see: https://webpack.js.org/plugins/...); there's an example literally showing what happens. Your frontend developer should have been aware of that.

Using the .env file in the frontend basically counts as a preprocessor directive (like constants in C)

There's many reasons for this. First: it's easier; second: it's safer. You don't want some dumb fuck to accidentally include the entire .env file as a dependency and end up showing your db credentials to the world.

But that's something the frontend developer should know, since it's clearly stated from the documentation (and you get to figure that out perfectly fine on your own when you're trying to learn the tools anyway).

@retoor poor Puff, we got a third cat and she's absolutely livid. Stopped entering a whole room altogether, I don't remember ever seeing her so offended.

@SidTheITGuy

BRIDGE PEER

${BRIDGEPEER}: bridged peer

- the bridged peer

@atheist A LONG ERROR STACK IS JUSTIFIED IF I'M USING C++ TO SOLVE COMPLEX STUFF

THOSE 6 PAGES OF STACKS CAME FROM SHOWING A FUCKING LOGIN FORM

@BordedDev no, I would argue a kick in the balls would be better than this repulsive ball of mud. The vast majority of that is just rxjs being the worst project manking has ever conceived.

I feel like a broken record sometimes but I still believe this whole angular thing is a prank and it's just a matter of time before some hidden cameraman pops out laughing "HAHAHAAH WE TOTALLY GOT YOU! WOULD YOU REALLY BELIEVE ANYONE WOULD BE MENTALLY RETARDED ENOUGH TO CREATE THAT?", we all get a beer together and then talk about what the industry is actually doing behind the curtains of a good joke.

@lorentz this was on one of our staging environments, we don't take source maps there but that's not the problem. The problem is a call stack 20m long for one http request; the kind of stuff you'd be entitled to expect when working with a framework designed by human beings instead of actual retards.

@Lensflare I'm a Halo fan, and I got hooked up with the recent wave of ShinRegis memes. "By the rings" is one of the things the Arbiter says after some particularly bad pun by the Master Chief (EG: https://youtube.com/shorts/...)

@Lensflare I said what I said

@retoor Someone programmatically creates a component with some configuration -some weird custom form builder we have, and someone will have to pay for this someday but I'm not quite there yet- , somewhere in the life cycle of this component it fires this HTTP request. Need to decode where that happens, the call stack of Angular is nested 400 times.

And no, it's not a problem with compilation; if I did that with any sane framework, I wouldn't have to deal with this shit.

When even cock and ball torture isn't enough to make you feel anything, this is when you start going to Angular

Google brought me here years later, and boy is this absolutely what I needed to read

Men will institute a democratic process for achieving a shared consensus among LLMs before going to therapy

Because it's meant to be an exchange language and not every language supports that (how would NaN even translate to C?).

Javascript Object Notation means every JSON counts as a valid JS variable, not the other way around: not every valid JS variable instantly counts as JSON.

You can't serialize functions, you can't serialize NaN, you can't serialize Infinity. Seems pretty straightforward.

@tosensei it's not a hot take, coming here definitely counts as sticking my dick in a toaster

I'm bald, and all bald men with a beard look exactly the same

@antigermanist thank you technically correct man

Also: I, of course, oppose male circumcision. It's a barbaric practice, no matter how you frame it, and should be allowed only for certified medical reasons

WITH THAT BEING SAID

If you can't tell the difference between "removing a piece of skin" and "literally choppping off an entire organ", you might want to consult a lawyer and ask your parents for compensation, as you might be genuinely retarded.

If the only rebuttal to "you shouldn't slice off the clit of your young girls" is "no you don't understand, you're white" you're literal subhumans and shouldn't even be allowed to decide the brand of soda you drink.

I said what I said.

@iiii I use GPT up to once per month, maybe, but this guy listens uses it a lot -or, rather, a lot more than he should at any rate.

By dumb luck, it turns out GPT agrees with me, and of course I'm going to use that.

@Demolishun

> you expect me to believe this? does it look like I have "fucking imbecile" written on my forehead?

> you see 3 senior members of the team doing each 90m overtime per day (one of them is me, that's why I'm so bothered), you see the whole team struggling to keep up with the tickets, when we ask "where's the new hires, we can't keep going on like this" you start blabbering nonsense about uncompiled timesheets, did we take the entire management straight out from [local mental asylum]?

> you're working in a software development company and claim you can't check the patch notes once every 3 weeks, I can't be the only one wondering what the fuck are you people even doing in this life

@iiii I must have missed it. Either I wasn't paying attention or recording started before I got there, maybe I joined a minute later or so.

@Lensflare this is not a boycott. This is me preventing myself from being instupidified by an instrument that does the thinking for me.

I allow myself some AI if the time calls for it -most of the times, it's when I don't even know the name of what I should be searching for-.

Ok, so, analysis: there's at least two files writing on the singleton with the wrong behavior; you may patch one, the other will still write the same thing.

So I need to patch both of them (one is 1200 lines, the other is 1800 lines), and the second is some unreadable clusterfuck of intertwined connections, the current situation being the result of tens of tickets and business requirements nobody ever bothered to write down -a good part of which is entirely lost to time as moving the repository from GitLab to BitBucket lost the history so I can't reconnect any line of code to whatever ticket originated it. There's no way I can touch this shit without us getting sued. Wish me GL.