New job
New project
Main React component file
20028 loc
Can’t make this shit up

Client says the styling of a particular component on their website is wrong. It looks fine to me. They can't give me an example of how it should look, or tell me what's wrong with the way it looks currently, but they want me to fix it.

So we've got a gif that doesn't show up in our React Native application. Of course, the designers assume it's me: "are you sure the gif is in the codebase? how are you using it in your component"? yeah ok boomer. I'm like, look at this other gif, works fine. "oh" So I tell them, double check the export options on how you are building the gif, maybe there is something there. so now they are asking ME for those export options. I'M A DEV, NOT A DESIGNER, DO YOUR JOB AND FIGURE IT OUT. I DON'T EVEN KNOW WHAT PROGRAM YOU ARE USING

oh as an aside, I was putting up a website for a client and they are like "my logo is quite similar to many others, is this something to worry about legally?" OH, SO NOW I'M A LAWYER TOO??!!?!? WHAT IS WRONG WITH YOU PEOPLE GOOGLE IS LITERALLY IN FRONT OF YOU

why do people continually think just because we can code we are fucking designers / lawyers / astronauts
/ god?
man this pisses me off - i think of that draw red lines with blue ink expert video, in the end, just smile and nod: "i can do... absolutely anything... trust me, I'm an expert"

Question - is this meaningful or is this retarded?

if

2*3 = 6
2*2 = 4
2*1 = 2
2*0 = 0
2*-1 = -2

then why doesnt this work?

6/3 = 2
6/2 = 3
6/1 = 6
6/0 = 0
6/-1 = -6

if n/0 is forbidden and 1/n returns the inverse of n, why shouldn't zero be its own inverse?

If we're talking "0" as in an infinitely precise definition of zero, then 1/n (where n is arbitrarily close to 0), then the result is an arbitrarily large answer, close to infinite, because any floating point number beneath zero (like an infinitely precise approximation of zero) when inverted, produces a number equal to or greater than 1.

If the multiplicative identity, 1, covers the entire set of integers, then why shouldn't division by zero be the inverse of the multiplicative identity, excluding the entire set? It ONLY returns 0, while anything n*1 ONLY returns n.
This puts even the multiplicative identity in the set covered by its inverse.

Ergo, division by zero produces either 0 or infinity. When theres an infinity in an formula, it sometimes indicates theres been
some misunderstanding or the system isn't fully understood. The simpler approach here would be to say therefore the answer is
not infinity, but zero. Now 'simpler' doesn't always mean "correct", only more elegant.

But if we represent the result of a division as BOTH an integer and mantissa
component, e.x

1.234567 or 0.1234567,

i.e. a float, we can say the integer component is the quotient, and the mantissa
is the remainder.

Logically it makes sense then that division by zero is equivalent to taking the numerator, and leaving it "undistributed".
I.e. shunting it to the remainder, and leaving the quotient as zero.

If we treat this as equivalent of an inversion, we can effectively represent the quotient from denominators of n/0 as 1/n

Meaning even 1/0 has a representation, it just happens to be 0.000...

Therefore

(n * (n/0)) = 1

the multiplicative identity

because

(n* (n/0)) == (n * ( 1/n ))

People who math. Is this a yea or nay in your book?

A legacy custom made WordPress Theme.

Old developer made main styling sheet with 8000+ lines of code with no component separation.

To the reactjs-centered fucks who develop the popular web component viewing software called storybook: have you ever heard about semver?
89 alpha/beta/rc releases for a minor update 6.3 -> 6.4 with "100's of fixes and enhancements" "in preparation of the HUGE 7.0 release". Gee I wonder will it have 1000's of bugfixes? How bug-ridden is this software?
Every minor upgrade since 5.x is backwards-incompatible and requires a day of frustration finding out in how many more fucking NPM packages you split your codebase just because it's cool. I know move fast and break things, but some of us have other things to do than resolving node_modules incompatibilities you know. "No just hit 'npx sb upgrade' you say". I did, I really did! And the browser showed a blank screen of death with tons of cryptic React errors, it really did! Thank God you abstracted away all your dependencies in that sb command, now you can't even read the docs about what could have gone wrong with a specific sub-package. You have @storybook/html but the docs redirect to React pages, so good luck if you use something else

This is so sad... like.. the IDEA of storybook is great. But why did faith put the capacity to develop such a tool into the hands of people who think the world centers around React and JSX.. HTML should have been the default, and then you build on top of that for your fav framework, not the other way around

The day I realised There is an AngularJS before Angular 2

In our t ch stack, we have multiple components, most of them are backend, but 2 of them are fronnt end.

The first one is a straight Angular 4 application, and it has the normal angular structure, a ts file, a css file, a js file.

The other component, has a very weird structure I don't understand to this day.

It has a mix of js and html files, sometimes one inside another.

The js file has some "angular.core.shit" and I thought it should be Angular, but nothing in it resembles any angular project.

After much confusion, I finally came across an AngularJS website which is supposed to be deprecated last year.

Then I came to know of the story of Google taking ove rAngular and releasing Angular 2.

Nothing like client requesting "Hey can you add a virus scan for every goddamn file in the pipeline ? (We don't know what antivirus software you can use, neither do we know what are the consequences of this virus scan failing. We also don't know why a system admin is not doing this server wide instead of a software Dev doing it for this specific individual component. Heck we don't even know why do we need the virus scan in the first place) You might need to think 'outside the box'. Let's hope this is done by 12th Jan. Regards" on a Friday goddamn night

They probably even expect me to write my own antivirus software instead of paying for one

Why is industry like this ? Is there really any polite way to deny this ?

Anyone know why calling the "memo" function on a React component or using the "useMemo" hook is widely accepted to be called "memoization", when the name itself derives from an existing English verb which actually means what the function does? Why are we artificially creating jargon?

Can a React.JS expert help me to understand something?

In short, I would like to know what are the main differences between react version 15.6 and 17, in terms of browser issues, and component compatibility?

We have a legacy code base that is in version 15.6 and the team wants to upgrade it and I am attempting to argue with my dumb CTO to upgrade to version 17. However, I’m not versed in react, I'm just a PO and the CTO doesn't know anything but for some odd reason is adamant about staying on an older version. The developers gave me their opinion but I'm interested in an outside opinion.