bdashrad

Questions to ask your interviewer

Management

• What problem do you solve and why would I give you money to solve it?
• When’s the last time someone went above and beyond the call of duty at the company/on the team? What did they do?
• What are the current goals that the company is focused on, and how does this team/role work to support hitting those goals?
• What are the projects in this company you think are really key to its future and how would a motivated person go about getting on them?
• What do you see as your largest technical challenge currently?
• Pain Points beyond headcount
• What is a project you wish a new member of the team could take on?

JoeyBurzynski

58 bytes of CSS to look great nearly everywhere

When making this website, i wanted a simple, reasonable way to make it look good on most displays. Not counting any minimization techniques, the following 58 bytes worked well for me:

main {
  max-width: 38rem;
  padding: 2rem;
  margin: auto;
}

lizthegrey

default['sshd']['sshd_config']['AuthenticationMethods'] = 'publickey,keyboard-interactive:pam'
default['sshd']['sshd_config']['ChallengeResponseAuthentication'] = 'yes'
default['sshd']['sshd_config']['PasswordAuthentication'] = 'no'

stettix

Things I believe

This is a collection of the things I believe about software development. I have worked for years building backend and data processing systems, so read the below within that context.

Agree? Disagree? Feel free to let me know at @JanStette.

Fundamentals

Keep it simple, stupid. You ain't gonna need it.

cite-reader

This oral his­to­ry of pass­word stor­age on the Web orig­i­nal­ly ap­peared as a re­mark in the #in­fos­ec chan­nel of the Hang­ops slack—the con­ver­sa­tion had turned to a men­tion of “hashed, salt­ed pass­words” in a breach an­nounce­ment in a way that made me sus­pect at least some of our friends had not stud­ied the top­ic in de­tail. Sev­er­al par­tic­i­pants then en­cour­aged me to ex­pand the re­mark into a blog post, and now here we are.While I was around for some of this, much of it pre­dates my ca­reer; every­thing is as ac­cu­rate as I can rea­son­ably make it, but cor­rec­tions of gross er­rors are wel­comed.The first time peo­ple at­tempt to de­sign a Web lo­gin sys­tem, they will usu­al­ly de­fault to sim­ply in­sert­ing their users’ pass­words in their data­base. This so­lu­tion is sim­ple, ob­vi­ous, and wrong.The prob­lem is that data­base stor­age is not near­ly as pri­vate as we would all like it to be. Even the data­bas­es that we’d

DWSR

Helm attempts to solve a specific problem: How do you package up a bunch of Kubernetes manifests in a way that's (relatively) easy to consume.

For simple applications, this works out pretty well. You get a few knobs to tweak on the installation (such as whether or not you want the Chart to create RBAC resources), Helm renders a stream of YAML and then applies it to your cluster. Where this breaks down is when you try to do anything more complex, and that break down happens in 2 areas: Maintenance and Usability

Sufficiently complex (read: any) Helm charts can be thought of as a piece of software. It takes a series of inputs (the values) and produces a series of outputs (the YAML stream of Kubernetes objects). With "traditional" languages, there's facilities for syntax checking, static analysis, testing, etc. that help ensure the software both functions correctly now and in the future. The Helm ecosystem has some of those same things (e.g. helm lint) as well, however they're generally limited to treating th

kconner

macOS Internals

Understand your Mac and iPhone more deeply by tracing the evolution of Mac OS X from prelease to Swift. John Siracusa delivers the details.

Starting Points

How to use this gist

You've got two main options: