Most businesses are totally fine if they have a few hours of downtime. More uptime is better, but treating an outage like a disaster or an e-commerce site like a power plant is more about software engineer egos than business or customer needs.
If AWS is down, most businesses on AWS are also down, and it’s mostly fine for those businesses.
Agreed, this was delightful to read! I really appreciated how the author was open about naivety and blind spots. It made the contrast more apparent when they learned things. I'd love to read more by this person.
Yours.co | Lead Software Developer | ONSITE Utah http://yours.co
Yours.co is looking for a software developer to build and lead a small team of two or three other developers in building their platform for offline backup of cloud storage.
You will be the head of software development at Yours.co and one of the first full-time software hires. You’ll have the opportunity to build a team, establish a process, pick a tech stack, and help settle the age old question of whether to use tabs, spaces, or extra semi colons to indent lines. This is a chance to create the culture you want and grow as a developer and person.
Because the team is relatively small, this role will involve lots of coding with some management sprinkled on top. Your main job is to build great software through your own efforts and the efforts of your team.
We are not looking for a rock star ninja unicorn sorceress code-crushing 100x developer-god. Real human beings only please.
What makes Elm + Phoenix so good together? I use Elm professionally and love it, but a back end is a back end. Is the love just "I really like Phoenix?" The way people talk about it makes it sound like it is uniquely suited to Elm, which I don't understand.
This is the most honest comparisons of frameworks I have ever seen. It is really impressive to see Alex, who is on the Ember core team, speak about the strengths of React without straw-man arguments.
I'm working on a personal project, and I find myself struggling with some of the same problems.
1. No constraints. Since it is just me in my free time, no one can tell me what to do, but no one gives me feedback on what not to do.
2. No definition of success or failure. Am I creating a product that I want to exist, trying to polish my skills on the side, learn a new tech stack, or just goof around? Since I can just claim that it's a hobby project when it isn't going well (whatever "going well means"), I don't have anything holding me to a standard, since I haven't established it yet.
Any ideas on how to avoid aimless fiddling around on personal/hobby projects?
Glen gave an incredible presentation at Mountain West JS about his adventures doing cool things with gifs. He ended up with bpm syncing between gifs and music. You should definitely check out the talk when the videos get posted on Confreaks.
We have other fun things, like racks of servers processing live television to create and store thumbnails, tools to create games and other content around tv shows, etc.
We are a small-ish team of 13 engineers spread between Utah and New York. We communicate over team chat and screen-sharing to make remote people feel welcome. Our workflow is based around trust and helping developers be productive, which means flexible hours, remote friendly, loose vacation policy, whatever equipment you want among other things.
We are also still small enough that we don’t have tons of organized hierarchy, and passionate people can have a large impact on product, company culture, engineering practices, etc. We do 20% time, send people to conferences, and have Thursday brown bags to share things we learn. We aren’t perfect, but we try to make it a great place to be a developer.
Right now our backend architecture is lots of node.js, some Golang and a smattering of Python. MongoDB is our main data store, and we use RabbitMQ as a messaging layer. Our clients are built with iOS, Android, Angular, Backbone, and React among other things.
You:
We are looking for people that fit two main roles, but if you don’t quite fit but are still interested we are too!
1. Browser Engineer
* You know and love the browser platform
* You can use HTML, CSS and JS to build great experiences
* You have worked with one of the trillion browser MV-whatever frameworks
* You have experience with the modern web dev workflow (build tools, modular js, css transpilers, etc)
* You enjoy keeping up with the firehose of new developments in the web.
* You are willing to be taught and teach others
2. Senior Android Developer
* You have built Android apps you are proud of
* You have in-depth knowledge of Android platform
* You have experience creating/using custom views
* You have experience making responsive UIs that fit all screen sizes
If any of our tech stack or problem domain interests you and you don’t fall neatly in to one of these roles, talk to us anyway. We are always open to good people.
If AWS is down, most businesses on AWS are also down, and it’s mostly fine for those businesses.