ajones

It isn't an error. If you click into one of the individual data sources (links available on the home page), you see messages like this:

> This page is being updated. It will post records of White House visitors on an ongoing basis, once they become available.

> This page is being updated. It will post records of White House staff salaries as the data becomes available for the Trump Administration.

LearnVest | New York (NYC), NY | ONSITE

Infrastructure Engineer - http://app.jobvite.com/m?3sglUhwJ

We are currently a team of five that focuses on the construction, maintenance, and automation of LearnVest's web operations. We are expanding the team in order to have more bandwidth for the exciting projects that we have in our pipeline. We spend a lot of time working with Docker, Kubernetes, Jenkins, Python, and AWS.

Some problems that we are trying to solve include:

* Migrating our monolith to a microservices model

* Leveraging our centralized logging infrastructure to quickly discover anomalies from deployments or environment changes

* Creating Ansible plays that help us achieve an immutable infrastructure

-

If you have any questions, please reach out to me at ajones(at)learnvest(dot)com

LearnVest | New York, NY | ONSITE

Software Engineer - Developer Infrastructure (http://app.jobvite.com/m?3O1EThw8): I'm building out a team that is focused on internal tools and our build & deploy systems. This team sits inside of our infrastructure group and is building tools that are used across our rapidly growing organization. Our ideal candidate has experience with continuous integration, Python, and Ansible.

Infrastructure Engineer (http://app.jobvite.com/m?3sglUhwJ): My group is also adding an infrastructure engineer to help us build the next generation of our systems. If you're in NYC and passionate about building highly available and scalable systems, let's talk! We're using Kubernetes, AWS, and Ansible to push LearnVest to the next level.

Depending on the technical abilities of the person using the solution, I would recommend one of the below two systems:

- Chartio: A good tool for someone who isn't very technical to discover insights. Drag-and-drop interface.

- Periscope: A good tool for someone who is able to write SQL to build visualizations from their queries.

You inflated numbers from your initial calculations, but I don't believe you inflated them enough. How do you expect a team of 20 to recreate an entire company in one year? Here's some things that I believe you missed:

- You need a team of product and project managers to put in time to plan the product and a high-level road map. The more granular product decisions are able to be performed in parallel to the build, if building the product in an agile fashion.

- Etsy has an amazing engineering culture that cannot be constructed if the developers are just focused on delivering the product. This culture has lead to many internal tools that help with site reliability.

- Etsy has already built a team of strong contributors. If Amazon were to build their own Etsy-like marketplace, there would be recruiting costs and false positives which will slow down delivery.

This list could go on and on, but is meant to illustrate that there's more to this sort of project than engineering, marketing, and infrastructure.

I know that they also support MySQL. We have Periscope connected to a MySQL database.

The tech and talent at Etsy would bring quite a bit of value to any company that were to acquire them. Their tech culture is top notch. I've followed their blog (https://codeascraft.com/) for a couple years now and have gained a ton of knowledge from it.

Some selected blog posts:

- Leveling Up Your Organization with System Reviews (Their latest post. https://codeascraft.com/2015/12/21/leveling-up-with-system-r...)

- Fault Injection in Production (http://queue.acm.org/detail.cfm?id=2353017)

- Q3 2015 Site Performance Report (Posted every quarter. https://codeascraft.com/2015/11/10/q3-2015-site-performance-...)

TL;DR a collection of TL;DRs for common *nix commands with clients to display the shorter docs

Being Geek by Michael Lopp

Rands does a great job at giving a broad range of career advice for software engineers. I also recommend his blog: http://randsinrepose.com/

The American crocodile is mostly found in Central America and the Caribbean, but also exists in the Everglades. I'm pretty sure it is an endangered species.

Stammy's articles are always a great read. As a developer, I appreciate his perspectives on the intersection of programming and design. I recommend his three-part post on designing and developing a responsive, retina-friendly site.

http://paulstamatiou.com/responsive-retina-blog-design/ http://paulstamatiou.com/responsive-retina-blog-development-... http://paulstamatiou.com/responsive-retina-blog-development-...

That's interesting. Many articles I've read state that the VP of Engineering tends to be more hands off, technically, than a CTO.

Here's a couple great articles that I've pointed people to on a couple occasions: http://www.bothsidesofthetable.com/want-to-know-difference-b...

https://medium.com/engineering-leadership/defining-roles-cto...

By this sort of thing do you mean using it as a data warehouse? That's what Redshift is branded as and the performance gains are definitely similar to what the blog outlines.

In my opinion, Redshift is the best data warehouse solution for a team building a small to medium-sized warehouse. This covers most use cases. For those building a data warehouse above a petabyte in size, you're going to have to look at different solutions. Redshift is powerful and relatively cheap compared to its competitors.

Their careers business has the opportunity to be a revenue generator for the company. The starting cost for a job listing is $495 per 30 days and goes up to $1499 per 30 days. In my opinion, the profiles on Stack Overflow careers allow developers to present themselves much better than many other career sites.

http://careers.stackoverflow.com/products/listings

Thanks for the response. I agree with your thoughts on hiring. I'm one of those guys who came in and learned Scala. The initial reason for my team using Scala was, "Why not?" Since that time, my colleague who hired me has left the company and I have been the lone engineer on the team.

We're currently looking to hire a second engineer and have also been rethinking the direction of the data engineering team. Changing the language to Python was a suggestion for the hiring factor and because it is the popular language for data engineering. Scala has been a fun language over the last year and a half and I wouldn't mind sticking with it because it has been fun. For that reason, I have spent time comparing the two languages for data engineering and haven't come to a consensus on which one is ideal for my team.