😭😭😭😭😭😭

As I started learning React, I found the allure of declarative style of programming appealing. I try to avoid maintaining multiple state variables for data that can be derived from the base state itself that's stored in the redux store. It works wonders when I have to change something; as I just need to make changes to one function in the utils folder and that change is implemented across the whole app, rather than change the instances everywhere as was the case when I initially started working on this project after the previous dev left.

But I see myself redefining a lot of computed values everywhere, and if I just try to define them in the root component, I'll end up with a huge list of props being passed to a couple of components. Shifting it to the utils folder helps a bit, but then I find myself defining even the simplest of array filtering methods to the utils folder.

Is this need to define computed values everywhere a trade-off that you need to accept when you write declarative code, or is there a workaround/solution I am missing? As of now, the code-base is much better than how it used to be when they had a literal Java dev work on React with their knowledge of Java patterns being used in a framework that is the polar opposite of OOP, but I still feel like there's room for improvement in this duplication of computed values.

Is OSS code worth it as an alternative to VSCode?

Found about the open source version a few days ago, and deciding to use this instead of VSCode on my new Manjaro distro(was using VSCode on Ubuntu previously). I did read through the differences as mentioned in the VSCode wiki, but I'd like to know what people here think of it.

I was genuinely baffled by this until I read up more on regex flags and realised that this is the intended behaviour😂

I didn't get a Google foobar invite for all my years of working on professional projects, but I did when I was trying to put together a web scraper because I was bored. Anyways I got a job shortly afterwards so didn't really bother with it.

Man I hate how CSS is treated differently on different operating systems using the same browser, let alone making the same UI heavy application perform identically on android chrome and iOS Safari.

Messing around with the css to figure out what all properties are treated differently, this is how the exact same code behaves on chrome on iPad versus Linux.

Look, I'm not a CSS genius, far from it, BUT it really shouldn't be this bad to make a responsive UI heavy application work on all platforms. I've been at this for weeks now.

Looks like someone got overconfident in their infrastructure's reliability and deployed on Friday.

Saw-ftware engineering horror movie concepts

Uh oh

Pain. Nothing but Pain and Suffering.

Doing someone else's Code Review in my project: "You must retain the holiness and piety of the code you write by following PascalCase naming for files and kebab-case naming for CSS variables. Avoid using duplicate strings by declaring enums in a constants.ts file and using that all throughout the app"

During my own Code Review in someone else's project: "WHAT THE FUCK DO YOU MEAN I CANNOT PASS FUNCTION REFERENCES AS PROPS TO A REACT COMPONENT AND ALWAYS NEED TO INVOKE IT INSIDE AN INLINE FUNCTION FOR THE PROP."
"WHAT KINDA FKIN DRUGS ARE YOU ON TO USE snake_case IN TYPESCRIPT DID YOUR MOM DROP YOU ON YOUR HEAD WHEN YOU WERE BORN YOU SACRILEGIOUS PIECE OF SHIT"
"WHAT DO YOU MEAN I SHOULD USE BOTH SINGLE AND DOUBLE QUOTES FOR IMPORTS AS PER LOCAL OR GLOBAL; I'LL SHOVE THE SINGLE QUOTE UP YOU WHERE THE SUN DOESN'T SHINE YOU FKIN DEGENERATE MORON"

As much as I do believe in self righteousness of my own coding conventions over others (I might be slightly better than others but I really can't claim good authority because I've had my lapses in conventions too; and being one of the newer members of the team certainly doesn't help, despite my boss supporting my initiative), I guess it is high time we bring in some already established code conventions in the team that is finally big enough to warrant them. Maybe AirBnB.

Ahh the gems you find in codebases where only one person each is in charge of the frontend and the backend.

Not sure if it is the difference in the state of my mind or if it is the gradual reopening of the markets, but it's weird to me how a couple of months ago when I was looking for a job change, I could hardly find any good opportunities; but now that I am well entrenched in the current job I have, I keep getting random leads for decent job opportunities for the very profile I work in.

Being able to make dev time estimates that aren't off by whole weeks.

Testing a script embed plugin I am building on various random websites, and came across this.

Like, bruh; have you ever heard of a javascript map? Basic functional programming? Or even a switch statement?

It's the same statement, over and over again, but with different parameters. Even old javascript had enough tools to do this with at least a basic stench of "efficiency"

<assumption>If there are no fundamental laws constraining the existence of simulated consciousness</assumption>, I would throw in my lot in working towards developing an AGI.

Since there is infinite time to learn any skill and <assumption>it is possible to learn or invent whatever software or mathematical framework is required for such a goal</assumption>, I would get down to that, learning and creating various new forms of mathematical frameworks and required software tools.

<assumption>Engineers usually work best without another fellow human on the project</assumption>, so I will set up automation for tasks that do benefit from multiple minds on a project, in the form of low-level artificial intelligence that I have to work on as a prerequisite for the main goal.

Once the critical mass is hit where the code can keep self-improving and produce more iterations of itself that are better, I sit back and start with my long, long to-watch/to-read list and try to finish as much as I can before the AGI I created would <assumption>repurpose all of our mortal flesh for more efficient use.</assumption>

The only remnant of the existence of humanity will be the influence on the initial design of the code based sentience that exists now.
.
.
.
.
.
.
.
Just kidding, <not-an-assumption>I'd probably procrastinate right until the heat death of the universe</not-an-assumption>

That adaptation serves well when repurposed for a programming job 🥴

The zuckerweb.ai knows what goes on in your deep subconscious

If you're gonna contact me on LinkedIn asking me to ditch my current job in favor of working for your company, you better make sure that at least the website on your company's LinkedIn page actually is up.

It's a form of artistic expression for some people (like me) who aren't as great with paper and pen but still have ideas and patterns and concepts and abstractions to express.

Watching the data just flow through the pipelines and pathways you've laid down for it, creating spectacles from what is essentially electricity running through a rock. Being able to create an interface between a human mind and an inanimate dead block of dug out and processed ore, feels like tapping into the metaphysical.

(Yeah I'm pretentious with words)

React, it's declarative way of doing things, and the functional programming methodology it prefers.

Realized how much I've moved on from for-loops and class/object instance to maps, filters and immutability/observers when I worked on a Laravel project after so long and found myself forced to do things in the, erm, "PHP" way, despite spending my initial year and a half of programming working exclusively in PHP.

Sure, there's Class Components and imperative techniques in React but I had blissfully settled into using the flexible nature of doing things enabled by both native JS and React, with hooks, Lodash/Ramda and (almost fanatically) pure functions

Probably old but I feel this pain deep in my heart 😢

Am I seeing multiple month old posts on my feed here because I wasn't really using devrant much till like three days ago, or is it because I've spent so much time on it that all the recent posts have been exhausted?

Deactivated instagram a few days ago and switched over to devrant as the primary procrastination social media. This is a much better place but it feels slightly odd to comment on a month old post.

The debugging duck has been retired and instead has been replaced by the maven meow
(Yeah I just needed an excuse to share a cat pic)

I really don't mind it as long as the work is on track but damn it hurts to read the git commit messages with messed up spellings. In some cases it's not just that, but variable names, file names, etc. as well.

English isn't the first language in my country and a lot of people are not as proficient with it so it's probably not appropriate to judge, but the cringe is real.

Sometimes I wonder if I am that cringeworthy person to someone else.

Windows is weird. Flagging a fully functioning game application as (Not Responding). It's not even lagging or freezing. It's just. Working. Perfectly.

Oh, how my colleagues think I have psychic powers and am able to discern what is the problem they face just by being notified of its existence.

I know I am guilty of this too, but it gets quite annoying when co-workers just barge in with a "something isn't working" while providing as few details as possible, needing me to ask them multiple questions about what exactly the fuck is it that made them cry.

Maybe it is a courtesy thing where you don't offload too much information in one go, but I wish they'd rather also tell me in what part of the application, doing what, with what input, did they encounter the problem.

Sometimes even I'll also just subconsciously assume a couple of details, only to realize fifteen minutes later that we're talking about two different modules.

The sorrow does not go away, one only gets used to it.