Or they shutdown and turn it back on, which doesn’t count in windows as restarting unless you disable fast-startup. So you get annoyed tech support thinking the user is a liar and an annoyed end user that knows they turned it off and on again.
With a lot of solar equipment, the tech support has access to a lot of settings us installers don’t, so we’ve had times where we tell the tech that we’ve done everything we can, including restarting it (and with my experience with Generac inverters, restarting them can and will break something!), and sometimes it really feels like they do click a magic button, say “how about now?”, then it works
As someone who has been asked to restart the computer, even though I already did that before calling IT support… I internally sigh, but begrudgingly do it again just to appease their process. Because I assume plenty of people don’t do it and make y’alls life a tiny bit harder, when a restart would’ve fixed it
Also, how many are solved by making sure the power cable is not just plugged into the wall, but seated into the back of the computer as well?
well shutdown isn’t a full restart anymore, it literally saves your issues and reloads it when it turns on. so we have to doublecheck that too. it should count as restart, but doesn’t.
Honestly, I would try the restart first (cause it was easier/more automated), and then a full shutdown and power-up. It’s been many years since I called any IT support though, but that was mu process. Cause I hated having to call for help lol
I hear ya, and appreciate the info because I didn’t know that. I was saying that I would do both before calling, and then again when they asked me
But this was back in like 2004-ish, so I’m not sure what was best practice back then. I would just try it all before calling lol… going so far as to shut down and unplug for a few seconds or more
As someone working as on-site IT support for over 15 years, I can’t tell you how often I have asked people to restart their computer over the phone and they swore they did (“multiple times even”), only for me to eventually come around to their desk and having them actually reboot the device in my presence and for the problem to actually fix itself.
One Lady I asked to restart their computer said “all right, hold on.” only to respond not even 10 seconds (!) later "I did, its still not working„ and after the third time I went to her desk and asked her to show me what she did. She leaned forward, turned off the monitor, then turned it back on. “I did this 10 times already, and its still not working”.
Some people just lie about rebooting, some simply don’t actually know how to reboot properly. After a few months, you get to know who’s lying, who’s doesn’t know better and who’s actually telling you the truth, you get to know your coworkers.
She leaned forward, turned off the monitor, then turned it back on. “I did this 10 times already, and its still not working”.
And this is why I couldn’t work in IT support; I just don’t have the patience for certain things. I always love teaching people new things, but most people don’t care when it comes to computers; they just want it to work effortlessly even when they’re the one screwing it up.
And especially working on-site! Oh my life, I bet there’s that same few people… just constantly failing to even try lmao
I swear I could hear the call center employee (probably not really an IT guy at this stage) sweating when I called them after a thunderstorm fried my router’s entry port and I read them the list of troubleshooting I already went through before calling them.
don’t commit credentials; split them up and place each part in a different place in the code and use code comments as a treasure map and make them work for it.
I also personally ask myself how a PyPI Admin & Director of Infrastructure can miss out on so many basic coding and security relevant aspects:
Hardcoding credentials and not using dedicated secret files, environment variable or other secret stores
For any source that you compile you have to assume that - in one way or another - it ends up in the final artifact - Apparently this was not fully understood (“.pyc files containing the compiled bytecode weren’t considered”)
Not using a isolated build process e.g. a CI with an isolated VM or a container - This will inevitable lead to “works on my machine” scenarios
Needing the built artifact (containerimage) only locally but pushing it into a publicly available registry
Using a access token that has full admin permissions for everything, despite only requiring it to bypass rate limits
Apparently using a single access token for everything
When you use Git locally and want to push to GitHub you need an access token. The fact that article says “the one and only GitHub access token related to my account” likely indicates that this token was at least also used for this
One of the takeaways of the article says “set aggressive expiration dates for API tokens” - This won’t help much if you don’t understand how to handle them properly in the first place. An attacker can still use them before they expire or simply extract updated tokens from newer artifacts.
On the other hand what went well:
When this was reported it was reacted upon within a few minutes
Some of my above points of criticism now appear to be taken into account (“Takeaways”)
Yes kids, the only stuff in ANY repo (public or otherwise) should be source code.
If it is compiled, built, or otherwise modified by any process outside of you the developer typing in your source code editor, it needs to be excluded/ignored from being committed. No excuses. None. Nope, not even that one.
Two choices: Either the production software isn’t in the exact state the repo was when the software was built. Or I can’t get build timestamps in the software.
Ironically, the worst thing I ever saw a coworker do was to change a function that accepted an Integer value between 0 and 32767 to one that accepted a Float between 0.0 and 1.0. Perfectly sensible change except that it resulted in a 120 mph knuckleball fired a foot above a 10 year old kid’s head, followed by a fist fight between the client and my boss.
Oldman.setHealth(0.0); //it is subunitary, but undefined behavior - will it access the ‘numeric value’ overload, or the ‘subunitary numeric value’ overload?
Use absolute number to remove the minus. Math.abs()
Oldman.setHealth(0.0); //it is subunitary, but undefined behavior - will it access the ‘numeric value’ overload, or the ‘subunitary numeric value’ overload?
Same result either way, so whatever if branch is first.
Understand the purpose. If you want to kill the old man with 0, then there’s no point to leaving it as 0.9%, understand the non-linear characteristics of life and death.
When you’re dealing with the low level functions, sure, you can keep it simple. When you’re reaching the surface of user input, you’re either going to waste time with validation and error reporting, or you’re going to waste time with interfaces that can handle more shit without complaining. There’s no fool proof either way, but good luck pissing users off with endless docs.
Don’t write your own code just yet.
If your goal in programming is just to be a traffic cop between the user input and the database, all you’re doing is building a virtual bureaucracy, the kind that people really hate and is easily generated with coding tools. Or you’re just deferring the “smoothing out” burden to the UI developers.
Yes absolutely, the parameter even if not in a strongly typed language should be a specific number and the unit should be implied. Overload the method to support different units if necessary or provide a unit as an additional parameter instead of forcing the method to parse the string for any unit type hints that may or may not be there
Why are females typed differently than males instead of a base class human with a gender identity parameter? Why would human anything have a function called young?? What would that function even do???
HumanFemales and HumanM both inherit from the Ape base class, it’s from an older java code base. We tried to change it once but it turned out the person that had written had retired and any changes we made just broke stuff.
I can accept your second point, but in your PR I would absolutely request you to rename the method to isYoung, and then in making said comment I would then ask… what value isYoung providing, and where is the line between young and !young ultimately for trying to get the dev to reevaluate the design. It’s hyper specific in an obtuse manner and I think it hints at design flaws especially with the perspective of product evolution
Well from my personal PoV there are a few problems with that
You can’t detect all credentials reliably, they could be encoded in base64 for example
I think it’s kind of okay to commit credentials and configuration used for the local dev environment (and ONLY the local one). E.g. when you require some infrastructure like a database inside a container for your app. Not every dev wants to manually set a few dozen configuration entries when they quickly want to checkout and run the app
I think it’s kind of okay to commit credentials and configuration used for the local dev environment (and ONLY the local one).
No. Never.
E.g. when you require some infrastructure like a database inside a container for your app. Not every dev wants to manually set a few dozen configuration entries when they quickly want to checkout and run the app
In this situation, it would be better to write a simple script that can generate fresh and unique values for the dev.
Hmm, I’m thinking - We should place a bunch properties and just name them something like “${username}” - “${password}” and variations of that, and see we can “find/replace” cross-site script them into sending their bots details
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.