Documenting EVERYTHING for the last week of my old gig, getting ready to go to work for Amazon Web Services! So excited!
Congats on finding your way in to Amazon. I know of at least one former and one current (myself) employee who follow Lobsters. I sit firmly on the other side of the house (consumer) but have worked closely with many AWS infrastructure and product teams in the last couple years.
Expectations are high, you will be expected to deliver, but honestly at the end of the day it is what I am looking for in an employer. YMMV.
Best of luck!
Thank you very much! With regard to being expected to deliver, I wouldn’t want to work in an environment that didn’t have that as a core characteristic. I get very frustrated working in environments where accountability isn’t considered a base principle.
Good luck. As Blake mentioned, there is a strong focus on delivery and other principles, which vary depending on level at which you join and your functions. My best advice to anyone joining amazon is to make the most out of broadcast, a “pseudo-youtube” containing tons of interesting information, in particular the ‘Principals of Amazon’ series. It’s by far one of the things I miss the most (along with having somewhat unmetered access to AWS)
OK, while I can appreciate people being excited about seeing OCaml in the wild, especially in places it might not often be used, but I have to wonder what it can actually bring to the table in cost/value terms over using a technology that’s custom tailored to operational tasks like Ansible, Chef or Puppet.
Ocaml’s advanced type system and safety aspects would bring additional safety to your “recipes” as compared other languages, such as the ones used in the tools you mentioned, i.e, Python and Ruby.
Might have some python work coming up, whats recommended testing wise? I’d like to try TDD, should I be using multiple libraries?
it forces you to use classes as if they were modules. After all it is a port of Java’s JUnit, and comes with the same symptoms.
I won’t defend unittest, but I will say that unittest.mock can be used independently and is a pretty nice mocking library: https://docs.python.org/3/library/unittest.mock.html
I blogged about pyrhon test runners http://www.holger-peters.de/why-i-use-pytest.html (doesnt include hypothesis though). But hypothesis can be a good complement.
It was a long holiday here in Ireland, so I spent some time working on a number of things, namely:
A couple of other bits and pieces around automation/improvement of my own development workflow.
Towers of Hanoi seems eminently studyable: the kind of interview question where if you’ve memorized the standard answer, or just the trick (“solve Towers of Hanoi with recursion reducing the size of the stack of discs”), you’ll ace the question, but if you have to figure it out from scratch, it may take you an arbitrarily long time, even if you’re super smart. Worse, it’s a problem which never comes up in practice, unless the temple in Kashi Vishwanath actually existed at some point.
For these reasons I think it’s probably a bad interview question.
Was ‘towers’ actually an interview question? Or was it just something the OP went deeper into after mentioning recursion in simple interview questions?
I feel this way about dynamic programming questions in general. Know the trick and/or study the ten or so archetypical questions, breeze through the interview. But there’s little chance you’ll derive the optimized solution from first principles. In either case the signal the interviewer get from the interview is pretty much worthless.
I couldn’t find any tag for testing. How can I submit a request to add the tag testing? (if it makes sense, which I believe it does, but YMMV)
Create a new post with the meta tag if you think it’s warranted. However, I think adding the practices tag to this post is sufficiently close to testing.
The Linux Programming Interface [Kerrisk]
Systems Performance: Enterprise and the Cloud [Brendan Gregg]
Plus browsing a few kernel books on and off to aid in a project filesystem I’m hacking on.
A couple of things planned, mainly around revamping the media center (my RPi2 just arrived today) - this time I’m planning to boot it with an open distribution and extending it to also bridge the skybox over the wifi adapter since I moved the router upstairs.
At work, I have been mostly getting my head around ansible, docker, netscaler and learning ruby/rails.
For space analysis, baobab is great.
I’ve been using jdiskreport for the last 10 years or so, it works a treat and it supports all main operating systems where the sun JVM runs
If you like strace, you might like ltrace even more. Strace dumps system calls, while ltrace dumps all calls into shared libraries.
ltrace also supports display syscalls alone or in conjunction with library calls, so you may not need more than ltrace
to be fair, he mentions one of my pet peeves about python, re the range() function