You can have a totally secure network and will never fail.

But nobody will ever be able to do anything useful on it because it will break every useful connection and ban every useful protocol on which most of your programs run.

Sure. I consider myself a fairly good dev. Not an amazing genius or anything but pretty competent in my area. Wouldn't have a clue how a load balancer works beyond what's in the name, I guess it balances loads. I can assume it does this by distributing requests to different servers because that just makes sense, but I don't even really know that. Networking might as well be black magic as far as I'm concerned. I'm grateful we have a decent infra team who knows about all that. So I'm not surprised.

tell that to the truckload of tape backups I just had e-wasted.

I've got one of those.

The most important skill is being able to talk to people and communicate... and being able to document shit in a useful manner for other people.

the technology skills are largely irrelevant.

where is the lemmy community for those who self-host chip fabrication?

everyone else is a poseur.

The very basic principles of 1 and 0 and using them to make logic gates is easy enough to understand. Its somewhere between doing that and getting hundreds of millions of them in a space smaller than your fingernail to all work at exactly the right way to send a specific series of them to space and back in a way that cant be interpreted by anyone but the intended recipient and then translate that information to a picture of someones dick that the confusion starts up.

it's all monads bro.

god bless Leibniz.

They are referencing an episode of The IT Crowd

Imagine a series of tubes. Imagine they are connected in a manner such that it spells "study computer networking: a top-down approach."

Those are the ones who can maintain eye contact, aren’t they?

Some developers that know both networking and developing will make those chips, the avarage developer will know about TCP/IP, DNS and those basics, at max

Once you understand how internet works, you will understand that it's also pure bullshit

we're all just faking it, hoping nobody looks under the hood

including your therapist.

How should i know that? I'm not american.

There’s a perfect way to do anything in frontend but only on the dev’s one computer. Everyone else will get garbage.

I think that people just can't make the software --> hardware jump. Like they understand what machine code is, and what CPU registers are, but can't understand how a CPU with baked in hardware instructions (i.e. a seemingly fully deterministic piece of hardware) can drive transistors to high or low voltages in a random way.

The key is to see all software as hardware, and to envision the CPU as many many light bulb switches, with some wired into each other, creating flip/flopping latches.

Once you get the idea of a flipflop, you can maybe then start to understand how all you really want from the switches is to output a switch configuration that encodes a value in some representation. The switches are all initialized in some state, but then drive a known flipflop path towards a desired value, and this happens millions of time a second, often in parallel with isolated switches, or with switches that are virtually segmented from each other, or switches that can chaotically interact with each other

The amount of math needed depends massively on your desired field. If you want to go into gamedevelopment you will probably work a lot with vectors. If you go into embedded systems the basic knowledge of hexadecimal and the binary system are crucial and you will probably also need the basics of electric engineering.

I would guess, that webdevelopment or systems integration usually don't involve that much math.

$130k after 2 years? 2 years after I started I was making like... $60k? That's not even counting the 4.5 years I spent starting a startup and making nearly nothing.

That said, I don't live in Silicon Valley or anything. Pretty low cost-of-living here. Probably a big part of the discrepancy. I didn't reach $130k until like 20 years of experience in the industry.

Inflation is thing that make number bigger but no more money. Less, even.

Imagine a series of tubes.

I just the other day got, an internet was sent by my staff at 10 o'clock in the morning on Friday and I just got it yesterday. Why? Because it got tangled up with all these things going on the internet commercially. [...] They want to deliver vast amounts of information over the Internet. And again, the Internet is not something you just dump something on. It's not a big truck. It's a series of tubes. And if you don't understand those tubes can be filled and if they are filled, when you put your message in, it gets in line and it's going to be delayed by anyone that puts into that tube enormous amounts of material, enormous amounts of material.

nobody understands fully how computers work

I mean, tap the breaks a little bit, here. "Fully" is doing a lot of lifting.

I will concede most people don't understand the concept of transistors, much less the electrical engineering that turns a series of transistors into a CPU. And I'll spot you that - for any given computer - it would take multiple extended papers to explain every piece of functionality.

But - broadly speaking - if you a computer engineer, you understand how a computer is engineered. If you're working in IT, you have enough of a functional knowledge that you can tell what each general component does.

And if you're a full stack developer (rather than someone who just does business logic on the backend), you should have a generalized understanding of client versus server versus database and how these pieces fit together. You should also probably have some grasp of the network stack, if for no other reason than you occasionally need to troubleshoot it.

It's a British show originally. Am USian, yet I've never seen the US version.

That's because an "IT engineer" is like an "engineer in chemistry". You have so many sub-disciplines that a given engineer can't be expected to know everything. Nobody is surprised if an organic chemist doesn't know much about heat exchanger optimisation, or a chemical process engineer is confused by organic synthesis.

In the same way, I've met devops guys that know surprisingly (to me) little about the intricacies of hand writing multi-threaded high performance calculation code. In the other hand, they're wizards at stuff like load balancing and optimising how we use sub-processes for I/O, CPU-bound or memory bound tasks. You would think the two are very similar, but even then it quickly becomes clear that people really become specialists in their field.

Neither am I. The show is British, but have you never watched a piece of foreign media?

This, Jen, is the internet.

You just launch Wireshark and watch packets going back and forth, and you understand it in like 10 minutes.

I think there are very few if any people who understand computers from the transistor all the way to front-end JavaScript frameworks. At least not deeply and not without major gaps.

Swears in z-scalar

The one correct way to do back-end is obviously to have lots of microservices all talking to a shared database so they can take each other down and also they’re never updated because you’d need about 10x the devs you have to maintain all of them. I know this because that’s everywhere I’ve worked for over a decade.

I mean, plenty of people use higher end coding languages to customize the tools they use to make advanced chipsets.

And, I'm sorry, but JavaScript isn't that hard to understand - intentionally so. It's one of the first languages you can learn in grade school.

I doubt anyone could go end-to-end on hardware manufacturing. But that's more an issue of parts miniaturization. People build working computer kernels in Minecraft using torches and switches.

It’s a series of clouds.

I’m an unprincipled engineer, in that case.

It’s funny that the follow-up to the “just learn code” movement that ignored the importance of knowledge was “just ask claude”, so now you don’t even have to write bad code to create a minefield of horrors in prod.

I know this is a joke, but most people don't realize the diversity of the internet specializations where if you're not in that specialization, you can't do it