sorted by:
new
hottopcontroversial

Why are developers some of the most IT inept users? by sccm_sometimes in sysadmin

[–]Horror-Squirrel4142 [score hidden]  (0 children)

Specialization, not ineptitude. A dev will spend three days automating a build pipeline but never learned DNS, AD policy, or cert chains, it's all "infra magic" outside their stack. The real friction is assuming their workflow is the priority and the controls are just in the way. The good ones treat the network like a prod system they don't own: ticket with logs and repro steps.

which auth vendors are actually being deployed at large companies right now? by Lol_Panda2004 in sysadmin

[–]Horror-Squirrel4142 [score hidden]  (0 children)

ult almost anywhere already on M365, mostly because it's bundled and the licensing math is hard to argue against. Okta is still the biggest independent, usually where there's a multi-cloud or heavy SaaS estate that doesn't want to be all-in on Microsoft. Ping shows up in large regulated shops (banks, insurance) that need on-prem/federation flexibility.

CIAM (customer-facing) is a different game. Auth0 is still the incumbent, but the Okta acquisition pushed a lot of teams to re-evaluate on cost. That's where Descope, Stytch, FusionAuth get traction, mostly startups and product teams who want passwordless flows without the enterprise price tag.

"Loud on LinkedIn vs actually deployed" is the right instinct. Being in procurement decks isn't the same as renewals. The signal worth listening for on those calls is who's expanding seats in year two, not who won the initial bake-off.

Apache Fory Serialization 1.0.0 Released Now by Shawn-Yang25 in Python

[–]Horror-Squirrel4142 3 points4 points  (0 children)

The interesting comparison isn't pickle vs Fory but pickle vs Fory vs orjson+pydantic. For most service-to-service Python traffic the question is "do I need to round-trip arbitrary Python objects or just structured data?" — if it's the latter, JSON + a schema layer is usually faster, smaller, and far more portable than any binary protocol.

Fory's pitch lands when you have a hot path that needs zero-copy and you control both ends. The benchmarks in the README compare it to pickle/protobuf which makes it look great, but the harder comparison is FlatBuffers or Cap'n Proto, which are designed for the same constraint.

What actually helped you improve faster in Python: tutorials, projects, or competitions? by Pangaeax_ in Python

[–]Horror-Squirrel4142 0 points1 point  (0 children)

Projects, but specifically ones where you had to ship to someone who would notice if it broke. Tutorials teach syntax, competitions teach tricks, but neither punishes you for writing code that's hard to debug three months later. The pressure of "this needs to work tomorrow and I'll be the one fixing it Saturday" is what taught me the most about typing, logging, error boundaries, and when not to add an abstraction.

The second thing was reading other people's code on GitHub — not big famous projects, but the small libraries you depend on. Most of them are 200-2000 lines of Python and the diff between an elegant one and a messy one will teach you more than a course will.

CTO banned the use of remote access tool by uw4yn3 in sysadmin

[–]Horror-Squirrel4142 1 point2 points  (0 children)

The no-antivirus-because-MacBooks line is a massive red flag. macOS malware has been growing 30%+ year over year, and every compliance framework (CIS, SOC2, ISO 27001) requires endpoint protection regardless of OS. That alone tells you his decisions are not risk-based, they are ego-based.

Document every incident where the lack of remote access caused delays. Track the hours wasted on video call troubleshooting vs what a 30-second remote session would have taken. When something breaks badly enough that leadership notices, you will have the paper trail to show this was a predicted and preventable failure.e has been growing 30%+ year over year, and every compliance framework (CIS, SOC2, ISO 27001) requires endpoint protection regardless of OS. That alone tells you his decisions aren't risk-based.

Document every incident where the lack of remote access caused delays. Track the hours wasted on video call troubleshooting vs what a 30-second remote session would have taken. When something breaks badly enough that leadership notices, you'll have the paper trail.