HN user

apenney

44 karma
Posts0
Comments17
View on HN
No posts found.

We had something similar happen with lifecycle rules, moving an entire bucket to glacier: end result was > $200k and AWS weren’t especially helpful on our attempts to refund us.

We were unaware that changes via a rule still count as an api hit per object, despite all happening in the backend. I’m sure we can’t be the only people hit by this.

You know, I feel like the perfect person to answer this. I used to be a sysadmin, then a devops engineer, then a "VP of Infrastructure", and I'm currently doing some hands on work again as a "lead devops engineer".

Like you, I used to be frustrated at my inability to program, and I felt like I could never make sense of any of it. I spent years in my earlier career sticking to "sysadmin things" because of that limitation.

Eventually, as automation hit the industry, I started writing more and more ruby code (we were Puppet users) and eventually I took a full time job for a year writing ruby code.

It was never an inability, it was always a confidence thing. I was scared to try and fail. By taking a full time position as a developer I -had- to succeed, and I like to think I did. I found it's not nearly as hard as I imagined, and the fact I did not have sysadmin duties competing made a HUGE difference. I was able to dedicate all day to what I was doing, not fit it into the corners of my life.

From what you wrote above, it's pretty clear that your personality woes (anxiety probably is the big one here) is convincing you that you can't do this.

I wasted years convinced that it was "too hard", but in reality I just didn't have the motivation to push through my discomfort. I don't actually write a lot of code these days, but I'm no longer afraid to pick up some code and modify it if I need to because I know it's just a matter of being patient and figuring things out as I go.

My biggest issue with SICP was the lack of available unit tests for the exercises. I'd often "get it wrong" and have no recourse but to read a solution to see that I'd failed to account for some aspect of the problem.

Without an easily verifiable way to test your solutions as you go I think these kinds of books really do themselves a disservice as you lose the ability to struggle and think hard about the problem if you can't immediately solve it.

I ran into something very similar with a cluster almost identical to you. Turns out the default disk size for kops is 25G and when your masters run out of space things start to die with almost no way of telling why.

I rerolled with 100G and I've seen zero problems since.

How do you judge those qualities? I too interview for a similar set of skills (intelligence, curiosity, a desire to constantly improve things, someone who's just willing to put in the hard slog as well as work on the fun projects) but it's incredibly hard!

I've definitely had people that interviewed well that just wanted JIRA tickets fed to them immediately upon starting. It's very hard to figure out if someone will seek out and make improvements consistently from the basis of conversations.

(I'm in ops so there's rarely a body of code available they can share for how they work, either.)

Maxwell Health | Infrastructure Engineer | Boston, MA | REMOTE | www.maxwellhealth.com

Maxwell is a health and wellness technology company in downtown Boston. We’re on a mission to transform healthcare in America by creating an awesome consumer experience for enrolling in, managing, and using benefits.

We're looking to transform our style of operating services at Maxwell and we're hiring Infrastructure Engineers to help us build out the technology and platform our engineers use to build, test, and run their services in production.

We're currently using terraform, docker, and ansible, (and jenkins) in AWS to deliver our SaaS platform. Any prior experience with these would definitely be appreciated by us!

If you're interested in helping us implement containers in Kubernetes, in transforming our approach to monitoring and metrics, or just in working closely with engineers to really build something you're proud of, come talk to me at ashley.penney@maxwellhealth.com.

Maxwell Health. | www.maxwellhealth.com | Devops/Infra Engineers | Full time in Boston, MA.

Maxwell is a HR and benefits technology platform that combines management and enrollment in benefits into one experience, aimed at small businesses.

(I just used it as an employee as I just joined Maxwell and it was pretty slick compared to my previous onboarding experiences!)

We're looking to hire an "Infrastructure Engineer" to help us improve our automation and operational practices. We're in the middle of transitioning from a traditional "devs build, ops run" environment to a microservice driven "devs build and run their own services" world. We're looking for experienced engineers who have either been through or worked on the other side of this transition to help us build, improve, and deliver building blocks to the developers.

We're especially interested in anyone with real world docker experience (I'd be double thrilled if you've played with Kubernetes) who has seen beyond the shiny marketing and experienced the world of pain that Docker can bring.

We're hiring locally in Boston at this time. If you're the kind of person that loves to pair up with engineers to help share your expertise throughout the team and really values a true collaborative environment then please come talk to me at ashley.penney@maxwellhealth.com. (or ashp on Freenode)

Am I doing something exceptionally wrong? I click Restore from file in scoped rules, and then decode recipe. That gets me more json on the left (in a red box, so I assume parsing failed). I then try "Import Rules" and nothing seems to happen. The commit button at the top never allows me to click, and nothing changes.

This is using the abp setup (and a few of the others in stuff/), none of which worked.

This is pretty timely, I tried and failed to get into Chapter 2 of SICP just a few months ago and eventually got discouraged and ran out of steam. I signed up for this, maybe it'll help keep me accountable and on track.

I'm in an air cast boot thing right now and until recently I was on crutches. I'd say 16% is about average for people willing to look me in the eye and speak to me. Most people deliberately avoid eye contact desperately so they won't have to offer you a seat.

I'm starting work at Puppetlabs in exactly a week's time as part of a brand new "module team" and I personally promise you here and in the open that I am going to tackle the puppetlabs-rabbitmq module and fix it so that it actually works and isn't an abandoned wasteland.

Come to that I'm hoping we can start building out a full set of mcollective modules to replace the existing ones that will be fully supported and kept up to date so that getting mcollective running will be as easy as including a class and waiting.

A huge part of this job is ensuring community patches get merged in and contributors get treated as I would like to be treated when contributing to a project. I hope we can reverse your experience with modules within a few months (I took this job because I've been in exactly your position, grabbing official modules and having them not work at all!)