In the US, a conductor is the one who checks tickets, makes announcements, and delegates tasks to the crew to help ensure things keep moving on time.
The locomotive engineer is the one who is “driving” the train. They run the engine and communicate with dispatch and traffic control to keep them informed where this particular train is fitting into the overall juggling act,. They also make every effort to keep things safe (watching for signals, obstructions, etc.).
I’m not 100% sure if the terminology is different outside of the Us.
(Source: My father is a 3rd generation locomotive engineer.)
Yes, driving trains is becoming more and more important as we find out how terrible cars are for the environment. We should protect the profession fiercely!
Which are used to calculate stresses for dams, fluid dynamics for planes and ships, capacity and load simulations for power, and to compile and operate servers.
Software engineers are the pinnacle of engineering.
Check out this book on Amazon (or your library) to see just how clever and useful we really are.
If you need a book to tell you how useful you are, chances are, it's claims might.be a bit overblown. The profession that has most of those.books written about them are managers after all. Just saying.
Software engineering doesn’t treat failure anywhere near important enough for me to consider it proper engineering. Bugs are expected, excused and waived, which for anything critical just isn’t acceptable in my opinion.
Bugs are inevitable. Humans can’t write more than a few dozen lines without making a mistake - it’s inevitable because we’re barely sentient apes, floundering to understand the full scope of the problem space
But through methodology, bugs can be mitigated. You can reduce their number, and fail gracefully. We have countless ways to do it, and we teach how widely
There’s a science to it all, and those of us worth our salt know it… It’s not our fault that management disregards our warnings and pushes ever tighter deadlines.
We know how to do better, our warnings just fall on deaf ears far more often then not
Meh. There’s a saying in my field: “anyone can build a bridge, only an engineer can make one that barely doesn’t fall down”.
Humorously reductive as it is, software is what makes that “barely” thinner than human calculation would normally yield. So… Yeah. Not what I’d call a pinnacle.
IIRC the train travels at a constant speed so you can make it faster by resizing your terminal so it’s narrower. Thus the train has a shorter distance to travel and the animation length is reduced.
Doubles have a much higher max value than ints, so if the method were to convert all doubles to ints they would not work for double values above 2^31-1.
(It would work, but any value over 2^31-1 passed to such a function would get clamped to 2^31-1)
To avoid a type conversion that might not be expected. Integer math in Java differs from floating point math.
Math.floor(10.6) / Math.floor(4.6) = 2.5 (double)
If floor returned a long, then
Math.floor(10.6) / Math.floor(4.6) = 2 (long)
If your entire code section is working with doubles, you might not like finding Math.floor() unexpectedly creating a condition for integer division and messing up your calculation. (Have fun debugging this if you’re not actively aware of this behavior).
The answer is obviously to require all users to change their passwords and make them stronger. 26 minimum characters; two capitals, two numbers, two special characters, cannot include ‘_’, ‘b’ or the number ‘8’, and most include Pi to the 6th place.
The modern direction is actually going the other way. Tying identity to hardware, preventing access on unapproved or uncompliant hardware. It has the advantage of allowing biometrics or things like simple pins. In an ideal world, SSO would ensure that every single account, across the many vendors, have these protections, although we are far from a perfect world.
Effectively, the other option is passwords, and people are really, really, bad at passwords. Password managers help, but then you just need to compromise the password manager. Strong SSO, backed by hardware, at least makes the attack need to be either physical, or running on a hardware approved by the company. When you mix that with strong execution protections, an EDR, and general policy enforcement and compliance checking, you get protection that beats the pants off 30 different passwords to 30 different sites, or more realistically, 3 passwords to 30 different sites.
Great! Now when I brute force the login, I can tell my program to not waste time trying ‘_’, ‘b’ and ‘8’ and add Pi to the 6th place in every password, along with 2 capitals, 2 numbers and 2 other special characters.
Furthermore, I don’t need to check passwords with less than 26 characters.
I work in IT. We don’t run CS here, but a bunch of clients of my old employer do. I had just shitposted about this fiasco in a discord server populated with fellow techs from that company, fired up lemmy, and this was the first post. What a fucking banger! I immediately shitposted again pasting this image. You’ve made my day. I need to stop using the internet because it’s all downhill from here. Thank you.
Fun story, my company just kicked off a PoC with crowdstrike 2 days ago. So far my computer was the only one that the agent was on as we had other work that needed to be done and we paused the rollout to the rest of my team. I woke up to boot loop hell today. Got it fixed right away, but so glad we didn’t roll it out any further. Not a good look to be starting a PoC with.
Sophos endpoint for years. We had an issue like this when we installed their software on one of Microsoft surface that use MS CPU we bricked every one of them. Kept Sophos and got rid of all the surfaces with Microsoft CPU.
If it’s any consolation, this is the first issue of its kind in the multiple years we’ve been using CS. Still unacceptable, but historically the program has been stable and effective for us. Hopefully this reminds higher ups the importance of proper testing before releases
For sure, my previous company I left last August ran CS for 3 years and we had no issues. Hopefully they hire a bunch of QA folks that were probably part of the layoffs earlier this year.
I mean it seems almost impossible that they either didn’t have a staging process to test N number of machines either virtual or otherwise or it passed through but it just seems insane that a problem of this magnitude went out to this many people.
Or requires a timestamp with zone offset, but ignores the zone offset, so you have to send the timestamp itself with a zone offset of zero relative to the systems timezone, but can’t just omit the zone offset, because it’s required.
When the API returns UTC, but mandates that you give it an offset which it will add or subtract from the UTC time, while still adding the Z at the end.
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.