zib

Good point, that is a valid way to do it sometimes, but it’s extremely situational and trying to do that for everything would be absolute nonsense.

I can understand telling you not to use break and continue if the point is to teach you to think about different ways to solve problems, but saying it’s because “it makes the code harder to read” is bullshit. Readable code flow is important, but if using those makes your code too hard to read, your problem is most likely that you’ve just written shitty code.

To get really into the technical weeds, what break and continue boil down to in the compiled machine code is a non-conditional branch instruction. This is just going to move the execution pointer to a different location in memory. Other keywords, such as if, elif, and else, will compile down to conditional branch instructions. Basically the same thing, but they have the added cost of having to evaluate some data to see if the branch should happen at all. You can achieve the same things with both, but the high level code might need to look different.

For instance, if you’re in a loop, continue will let you skip the rest of the code in the loop to get to the next iteration. Not a huge deal to instead make the entire code block conditional to skip it. However, the break keyword will let you exit the loop at any point, which is more complicated to deal with. You would have to conditionalize your code block and force the looping condition to something that would stop it on the next iteration. If you ask me, that has the potential to be much more complicated than necessary.

Also, good luck using switch without any breaks, but I’m guessing that’s not quite what your teacher had in mind.

In short, just go with it for now. Be creative and find a way to make it work to your teacher’s liking, but always try to be aware of different ways you can accomplish a task. Also, I don’t know what language you’re using, but if you’re in C/C++ or C# and you feel like getting really cheeky, it doesn’t sound like she disallowed the use of goto. It’s kinda like break with fewer safeguards, so it’s super easy to write broken code with it.

Personally, I found Arch to be difficult to get installed. I’m ok with command line stuff once everything is all setup, but having to use it for the installation process is something I found to be too easy to screw up and too time consuming overall. Also, I haven’t seen any drop of vanilla Arch with a GUI installer. For the Arch experience, I generally go with EndeavourOS since it’s easy to install, gives you lots of options for the window manager, and is easy to use once you get it up and running.

If you’d prefer the Debian environment, I think anything from Debian or any of its derivatives (Ubuntu et al) would be a decent choice. My favorite is Linux Mint. I’ve seen a lot of people describe it like “entry-level” Linux, but it’s very capable and user friendly. It’s where I tend to spend most of my time when running Linux and I would say usually requires the least setup since it typically just works out of the box.

There’s also OpenSUSE Tumbleweed if you feel like going a somewhat different direction. I get more “traditional Linux” vibes from OpenSUSE, but packaged up in a user friendly manner. I play around with it from time to time in a VM, mostly when I want to test out some new server package locally. But, that said, it’s still capable of handling anything else I throw at it, so it’s fun to use all the same.

I started out with blue switches years ago and they were obnoxiously loud, so I switched to reds and used those for a long time. Though, I kinda got tired of them and decided to give the Keychron banana switches a try several months ago and I’m absolutely loving them. They have a light tactile feeling, but they’re much quieter than Cherry browns. And a huge bonus is that Keychron keys are hotswappable, so if I get any bad keys or feel like switching to a new type, no having to deal with soldering to replace them.

This is really nice. I’ve been using Mint for years and didn’t know about it.

Wait, are you telling me that business ethics are actually a real thing? I thought somebody made that up as a meme. Every corporate executive I’ve ever worked for has been a borderline, if not full blown, sociopath obsessed with nothing more than getting richer at everyone else’s expense. Maybe they all skipped that class?

If you really need some nightmare fuel, some of us use c++ every day and even enjoy it.

In my experience, those things tend to be forced by project managers who believe the highest law of the land is proper scrum. Unsurprisingly, this makes all the devs miserable with no way to change anything because “this is just how it’s done”.

I do see a decent amount of activity on it. Full disclaimer, I am not a security expert. I know just enough to be dangerous. But, I see at least a few connection attempts from different IPs about every day. The top 3 countries of origin are China, Russia, and Brazil (based on the reverse DNS, but it’s possible some are using VPNs to hide their origin). My impression is they’re all bots that just go through a list of IP addresses, attempting to connect to the standard ssh port, then guessing the username and password. What I’ve found is they usually go through a list of likely ssh ports until one of them connects. Having the default port open to only the honeypot means they usually establish the connection, then leave it at that, so my real ssh port never gets hit. I kinda think of it like scambaiting, where I’m just wasting time they might otherwise spend trying to break into someone else’s real ssh server.

I have https open along with a non-standard port for ssh. Just for fun, I have the standard ssh port open, but redirecting to a Raspberry Pi running a honeypot. It’s fun to mess with foreign bots trying to access my network.

I’ve been working on a single bug for nearly 3 weeks. I think my “I’m getting closer to understanding this” is starting to lose credibility with my team.

Could also have been one of the devs who leaked it. Lots of us keep copies of the source for stuff we work on, so they may have figured it’s been long enough that no one would care if it leaked. However, I haven’t looked at it yet, but I imagine it would be most problematic legally if it contained proprietary 3rd party code. Leaking that could land someone in hot water.

I’m still fucking with the apache configs (I fucking hate apache…). As someone with no docker experience whatsoever, are there any getting started guides you would recommend for someone looking to make the switch?

Structured in the streets, object oriented in the sheets 😏