The same is true everywhere in tech, I swear.

"What if we abstracted away X?"

My dude, you're already operating on like five levels of abstractions, and you haven't the slightest clue how any of them work. The answer isn't another abstraction, it's learning how computers actually operate.

▲

grishka 17 hours ago | parent | next [-]

I once worked on a VK mini app with one guy. He was building the app itself, I did the backend. He just recently started learning web development, having never done any programming before.

So I'm ready for him to test my backend, I tell him to make a request to https://... and pass this and that parameter. And he just has no clue what I'm talking about. He somehow managed to learn React, a bit of HTML and a bit of CSS without any of the underlying basics. I had to explain him some of HTTP, the URL structure, and what an XMLHttpRequest is.

This was a revelatory experience for me.

	▲	Izkata 3 hours ago \| parent [-]
		I once had a co-worker admit he wasn't always sure which code ran on the server and which in the browser, in a PHP/javascript app that didn't use nodejs.

▲

willsmith72 17 hours ago | parent | prev [-]

Why? I don't care how the chrome engine works. I care about building a great CX and making money

▲

sgarland 16 hours ago | parent | next [-]

This is the difference, and why we can never understand each other.

I couldn’t care less how much customers like something; what matters to me is if it’s technically perfect.

This is also why I will never be happy at any job, because it turns out technical perfection doesn’t pay the bills.

	▲	16 hours ago \| parent \| next [-]
		[deleted]
	▲	grishka 15 hours ago \| parent \| prev [-]
		I generally agree with you, but if you only care about technical perfection, it can happen that something is "technically perfect", but insufferable to use. For example, I'm sure many of the common command-line utilities are considered technically perfect by their developers, but outside of some common use cases you've memorized, they are all a pain to use because of how undiscoverable CLI is by its nature. The "wrong input, go read some manuals" style of error messages doesn't help either. I myself always start from user requirements and work my way down from there.

▲

grishka 16 hours ago | parent | prev [-]

[flagged]

	▲	dalmo3 5 hours ago \| parent \| next [-]
		https://docusaurus.io If you think that's sluggish, that's a you problem.
	▲	willsmith72 16 hours ago \| parent \| prev [-]
		> I've yet to see a React website that doesn't feel sluggish and overall terrible I doubt it, sounds like confirmation bias.