As a data center engineer of 10+ years, I struggled to understand this at first. In my world, the hardware does a POST before the OS boots and has an inventory of what hardware components are available, so it shouldn’t matter in what order they are discovered, since the interface names should make a correlation between the interface and the pcie slot that NIC exists in.

Where the water gets muddled is in virtualized servers. The NICs no longer have a correlation to a specific hardware component, and you may need to configure different interfaces in the virtualized OS for different networks. I think in trying to create a methodology that is agnostic to bare metal/virtualized OSs, it was decided that the naming convention should be uniform.

Probably seems like bloat to the average admin who is unconcerned with whether these NICs are physical or virtual, they just want to configure their server.

Yup. You’ll see functions wrapped inside other functions all the time. The function on the inside will run first, then the next, etc.

In the example I gave, the value of nam is a string. But it you need to perform some mathematical function to it, it needs to be interpreted as a number. So once the value is received, int() will convert it into a number. Finally, that final value will be assigned to nam. Wrapping functions inside of functions is a great way to write concise code.

I think you need to look into string concatenation, the easiest and best of which is f strings. You could do something like;

print(f’welcome, {nam}')

You could also “add” the strings together.

print('welcome, ’ + nam)

Another thing, when assigning the output of something to a variable, you can think of it as “the result of the code right of the equals sign is the value of the variable”.

The input function assumes that the value should be interpreted as a string, but what if want it to be a number? You can just wrap another function around your input

user_number = int(input(‘what’s the number?’))

Your experience may vary but I’m a network engineer who learned Python and I think learning regex and pandas is invaluable. Depends on what you want to build though. As far as learning resources, I’ve always liked w3schools, it’s free and to the point.

For books, python 101 by Michael Driscoll is very good. I wouldn’t spend money on courses. They can be pretty demotivating and expensive.

I guess let people have their fun, but I agree. Class C space is pretty insignificant

Not trying to start an argument here but you sound very far removed from individual contributors, so maybe from your point of view it would simply look like adding it to a pile. More important than adding it to a pile is to make sure there’s systems in place to make sure OSs are patched. You wouldn’t be complaining to the IT/sysadmin guy about your servers’ vulnerability or patching schedules, you’d be talking to your cybersec department who’d have oversight. And if there’s a breach and your only defense is “I added it to the IT guys pile”, 100% you are getting fired as well.

I’m not a developer but I write a lot of code for network infrastructure automation… when I started learning I was already a network engineer so I figured it would be a cakewalk. I think it takes a certain type of person (patience, persistence, tenacity, etc) to excel in a computer science field. I’d reckon a lot of young people think the jobs are all pretty sweet and cushy

I agree with most of what you said but it wouldn’t hurt to create a watered down version of the site and put it on a subdomain like noobs.github.com … There can be separate UIs for different kinds of users.

They could ask when you register an account what you intend to use GitHub for and what your familiarity is.

Dude, thank you, totally agree. Anyone with skin thin enough to be hurt by this kind of corrective force shouldn’t even be in the conversation. Not sure why people are offended by this on here but when you engineer critical systems you damn well should know better by now.

Honestly, whether or not we agree with the approach of Linus, these kind of disagreements happen in the real world. Tensions run high. Recently I’ve been on calls where things need to be implemented this month, during a time where most of our resources(engineers) will be on vacation. These kind of conversations can be important to have to make sure this doesn’t happen again. The project management team got their ass handed to them for kneeling to the LOBs’ ridiculous timeline expectations. And they were told to hold the L if things don’t work on the go-live date, there will be no post implementation support until mid January if something doesn’t work.