I’d like some feedback from you: how much is too much? How much is good? Do we have a rule of thumb?
Arity is the amount of input arguments for a function / method / process / program. Less could be more… unless you write in Java and pass in a context object that holds hundreds of settings.
Arrakis, 10,193 CE: Paul Muad'Dib Atreides uses his abilities as the Kwisatz Haderach, "he who can pwn many servers at once", to run a large worm program on the Imperial Regional Utilization Local Area Network (IruLAN), enabling a privilege-escalation exploit which gives him root access to Imperial IT. The Bene Gesserit managers are furious; the Mentat sysadmins secretly admire Paul's hack.
Is growing your Dev/Ops skills important to you? Then my free, no-fluff newsletter will give you inspiration! It comes every Monday morning with my Mentor Monologue (a column on a specific topic I pick for each week), news from my DevOps community of practice "The Server Room", and a bunch of links to interesting engineering articles.
It’s been so long since I did anything with authenticated users, curious about “modern” patterns and standards.
Specifically, an authenticated user wants to do something. What patterns and standards are you using for permissions?
I’m seeing middleware mentions. But, curious what else is out there. Not looking for “use Framework X” and should be testable. Doesn’t need to be web-specific as I’m just looking for patterns and standards.
Fascinating article from IEEE Spectrum that discusses the carbon footprint of software and how we can both measure and improve it: https://spectrum.ieee.org/green-software
The benefit is not only less carbon, but following some of the principles that are outlined can decrease costs and improve efficiency.
The article references tools such as Firefox Profiler and Ecograder as well as an open source Sustainable Software Engineering course.