I just want to be clear, this was like highschool cs classes. I took things a bit more seriously in college.

I never wrote messy code or illogical code, or any code that didn’t work. We were learning C++ in those days and if you know anything about C++, you can basically cram an entire program into a single line. You can also do some shorthand stuff for calculations and updates to variables… So while the class was instructed to use whitespace and comments and update variables like “var = var + #” I would do var += #… I wouldn’t comment it, mainly out of hubris.

I was pretty good at it but I was lazy as all hell with it.

I don’t code, at best I script. I’m a sysadmin, not a dev, so I play around in PowerShell mostly.

I just started to naturally do all of this. Not because I was taught to, but because I’ve written too many scripts that I later looked at, and thought, WTF is going on here… Who tf wrote this? (Of course it was me)…

So instead of confusing my future self, I started putting in comments. One at the beginning to describe what the file name can’t, and inline comments to step me through what’s happening, and more importantly why I did what I did.

The sheer number of comments can sometimes double the number of lines in my script, but later when I’m staring into the abyss of what I wrote, I appreciate me.

I loved doing this is school, just trying to mess up my teachers.

Candles?

Why not gas mantles or something?

AI in the current state of technology will not and cannot replace understanding the system and writing logical and working code.

GenAI should be used to get a start on whatever you’re doing, but shouldn’t be taken beyond that.

Treat it like a psychopathic boiler plate.

It depends. If you’re forwarding a lot of ports then maybe, but just a home gaming server? Probably not a big deal.

Just don’t forward ports for remote control and you’ll be fine, especially RDP (3389 IIRC), and SSH…

I only had time to read a few paragraphs, but yeah. That’s a good one.

I’ll try to return to this and finish this reading.

You’re hitting on every point I could make.

My advice to anyone reading, and wanting to be okay in being wrong, the first step is admitting you don’t know something. Even if it’s something you should know. For example if you’re considered to be an “expert” or at least very knowledgeable about something and someone asks you about that specific thing, but it’s not something you know, avoid making things up, or trying to derive an answer from what you do know. Explain that you’re not sure what the right answer is, but you’ll figure it out, then do some research to figure it out. Don’t go off the cuff and start informing people of what you presume it is based on what you know, without knowing for sure.

The next step is when someone contradicts what you believe to be true, hear them out, then do whatever lookups and research you need to figure out if they’re right, or you’re right. Don’t immediately tell them they’re wrong, just listen, then find the truth and go from there.

The other thing I do, is I stay away from absolute statements as much as I can. Instead of saying that this thing I know is absolute and true, I preface it with qualifying statements like “I believe…” Eg, “I believe you need to use that switch over there to do the thing” rather than “use that switch to do the thing”. If you’re wrong then it was qualified as an uncertainty which can make a correction sting that much less.

Finally, always pursue the truth above all else. The point shouldn’t be whether you are right or wrong, the point is getting and giving true information to/from others. When getting seemingly true information from someone, trust but verify anything you’re told before passing that information along, whenever possible.

Always be learning, always be seeking the truth, always verify the statements of others. After a while, you’ll find that you’re right far more often than when you’re wrong… Having that kind of track record will help in your ability to handle the times that you’re found to be wrong and you’ll have a much easier time with it.

The whole thing is a process, so don’t beat yourself up over it. You will falter and catch yourself doing things wrong and making assumptions and providing information you later determine to be wrong. It will happen. Learn the correct information and move forward. When you lose, don’t lose the lesson.

There’s a ton more that I could say on the matter, but I think that’s the core points.

For me, I got a huge wake-up call while working at a large software provider doing end user support. I went to the escalation team and asked them about a problem, and they asked me about some of the details, when I provided them, they questioned “did you verify this? Or did you just take the customers word for it?”… I didn’t verify the information. They sent me back to verify the situation before they would engage on the matter, and IIRC, it ended up being one of the assumptions that the end user, or I made, which wasn’t configured correctly, that caused the problem. I managed to avoid needing escalation. From then on, “trust but verify” was a constant mantra. I’ve been growing and learning ever since.

The last comments in the image are exactly right.

It bothers me when I screw up and someone says “I fixed that for you” without explaining how I screwed things up, or how they fixed it.

If I’m wrong, I get it. I’m not always right, nobody can be right 100% of the time, IMO, that’s impossible. But when I’m wrong, let me learn so I can avoid being wrong in the same way twice.

IMO, schools have failed us, they teach us what we should know but don’t encourage us to always be curious and always be learning. It’s okay to make mistakes, and it’s okay to be wrong. What’s not okay is never learning from your mistakes, and being so stubborn that when you are wrong, you double down on being wrong instead of seeking more information so you can be correct next time.

Being wrong is always condemned. You get low grades, you fail and get held back in some cases… It’s been rare that any teacher I’ve ever had would review anything from a test after its over. A very small number went back and said “a lot of people had trouble with x question from the test, here’s the answer and this is why it’s the correct answer”. IMO, that should be way more common… Review the test after its over and let the class know that low marks are not the end, they’re a wonderful beginning to learning. If you know what you don’t know and you have even the smallest amount of ability and willingness to improve, with the addition of opportunities to learn that, then you will always succeed.

Be successful. Get a bunch of shit wrong.

Well, I’m probably going to try to get my ccnp for kicks. I’ll re-do my CCNA, then do my ccnp. By the time I go for my NA cert I’ll pretty much be ready to go for the np cert.

I’ll build a new resume emphasizing my network stuff, though my resume is already fairly heavily focused on networking as is, and try again.

I’m pretty happy with my job in almost every way, I know most of the things I would need to know to be successful, despite it being a more generalist position, and my co-workers are cool. Management is better than most, and the pay is more than the last two generalist positions I’ve worked, plus it’s work from home, so I’m pretty comfortable where I am for now. The pay, despite being higher than I’ve gotten previously, is a pretty far cry from what I probably deserve, just way too low, under $55k USD (I’m not in the US, but the conversion puts me under 55). From what I’ve seen online, median salary for a systems admin, which is basically what my job mostly entails, is around $73k USD… So I’m around $20k/yr shy.

I know network admins are similar, depending on the complexity/importance of the network they administrate. I’m aware of people in networking that are making more than 100k USD a year; and right now I consider that to be where things start to cap off for networking. I’d be pretty happy with $73k USD.

Yep, I’m sure they do.

Realistically, does any average consumer know what’s on which circuit?

Spanning the split phase will screw you up, across breakers won’t be fun but shouldn’t pose any serious problems, as long as it’s not in different sides of the split phase.

I’m pretty sure they say this because actually explaining what will work and what won’t either requires significant prior knowledge of power systems, or a couple of paragraphs of explainers before you can get a rough picture of what the hell they’re driving at.

Everyone I know who has used powerline, just plug it in and see if it works. Those who were lucky, say it’s great and works without issue, etc. Those who were not lucky say the opposite.

I’m just over here watching the fireworks, eating popcorn.

What, like the CCNA? Which I achieved and it expired last year, and got me nowhere?

I prefer linkin_park_numb.mp3.com

It just hit different

I feel this, especially since I’m more into networking, but my work is more generalist.

I open my mouth about networking and people’s eyes glaze over. Even very experienced senior people can’t really understand what I’m talking about when it comes to some of the more intermediary networking concepts. Meanwhile I tune into a podcast that’s networking focused and they’re basically speaking Latin for me.

There’s so much that I don’t know. I get the broad strokes of things but I’m hopelessly lost on so many of the more nuanced bits of networking.

I really want to break away from generalist work and get into a network focused position, but after 10 years as a generalist in various MSP companies, most places won’t take me seriously as a networker and won’t even sit down for an interview.

I’m good at other stuff, damn near expert level with some things, but my passion is networks and the workplaces I’ve been at just don’t care to help me learn any of it. My current place barely has any networking more complex than a profile based L2L VPN… Switches are basically ignored, and VLANs are rare.

I facepalm every time I discover that the guest network is just bridged into the same subnet as the LAN. I’ve raised the issue a few times and never been given the green light to fix it, often because the network isn’t able to be managed remotely.

You kids. Got off my lawn. Leave me in peace with my scour.net.

I don’t think either answer is wrong.

I’ve been doing IT work for more than a decade, I was a nerd/“computer guy” well before that. I’ve had a focus on networking in the past 15-20 years. You learn a few things.

I try to be humble and learn what I can where I can, I know that I definitely do not know everything about it, and at the same time I try to be generous and share what I’ve learned when I can.

So if you have questions, just ask. I either already know, or I can at least point you in the right direction.

It definitely sounds like you have some challenges ahead. I personally prefer MoCA over wireless, simply because you can control what devices are able to be a part of the network, and reduce the overall interference from external sources and connections.

With WiFi, being half duplex, only one station can transmit at a time (with come caveats). Whether that station is a part of your network, or it is simply operating on the same frequency/channel, doesn’t matter. So in high density environments, you can kind of get screwed by neighbors.

MoCA is also half duplex (at least it was the last time I checked) so having a 2.5G MoCA link, to a 1GbE connection (on the ethernet side) should provide similar, or the same experience as pure ethernet (1G full duplex)… The “extra” bandwidth on the MoCA will allow for each station to send and receive at approximately 1Gbps without stepping on eachother so much that you have degraded performance.

However, it really depends on your situation to say what should or shouldn’t be setup. I don’t know your bandwidth requirements, so I can’t really say. The nice thing about ethernet is that it on switched networks (which is what you’ll be using for gigabit), the. Ethernet kind of naturally defaults to the shortest path, unless you’re doing something foolish with it (like intentionally messing with STP to push traffic in a particular direction). The issue with that is that ethernet doesn’t really scale beyond a few thousand nodes. Not an issue for even a fairly large LAN, but that’s the reason we don’t use it for internet (wan side) traffic routing. But now I’m off topic.

Given the naturally shortest-path behavior of ethernet, of you have a switch in your office and you only really use your NAS from your office PC, you’ll have a full speed experience. If nothing else needs high-speed access to the NAS, you’ll be fine.

Apart from the NAS or any other LAN resources, the network should be sufficient to fully saturate your internet connection. So the average WiFi speeds should be targeted towards something faster than your internet link (again, half duplex factors in here). I don’t know your internet speed so I’m not going to even guess what the numbers should be, but I personally aim for double my internet speed for maximum throughput on my WiFi as much as I can. The closer you can get to doubling your internet speed here, the better. Anything more than that will likely be wasted.

There’s a ton to say about WiFi and performance optimization, but I’ll leave it alone unless you ask about it further.

Good luck.

It can be faster, it really depends on whether you have a clear-ish channel for the mesh, which is why I would recommend something on the higher end, hopefully with a dedicated radio for mesh, so it can be on a different channel with (hopefully) less interference.

If the mesh radio is shared with client access, or if it’s on a busy channel, it may be much, much slower than some options.

Hello friend.

You can get 2.5gbps MoCA now. You may want to consider upgrading.

Nice username btw