champion

Cool! I frequently prefer drafting presentations in markdown and it would be handy to to turn them into nice looking presentations

Good post with real numbers. Also has useful projections spreadsheet for download

This seems great. In the past I had set up Flickr to at least email all my daughter's grandparents so they could see new photos of her. As Flickr is dying and this case doesn't seem well handled by Instagram/Google Photos this seems like a really nice way to share family photos with everyone.

One of my favorite West Wing moments. So good.

I'd never heard of Donor Advised Funds before. I'd be curious if others have had a similar good (or bad) experience. I'm thinking I might do it for 2017 and wondering if there are any other things to be aware of.

For a side project I've deployed some simple endpoints to Heroku and used Spark (http://sparkjava.com/). Spark is a Java Sinatra clone rather than full Rails.

That said, not sure I'd pick it for simple side-projects. Part of the benefit here is how it works for a large dev team, with a large codebase, etc.

This is a good place to start: https://github.com/cxxr/better-java

The post mentions a few: Dropwizard for RESTful APIs (http://www.dropwizard.io which includes a bunch of good libraries), Guava, Guice, Hysterix, etc. We use Kafka for stream processing, Hadoop for batch processing.

I work at HubSpot, and was among the initially skeptical from having had bad experiences in Java in the distant past and spent more time in Ruby in the years prior which I mostly enjoyed.

The Java ecosystem truly saved itself from its own enterprise madness. Libraries and frameworks today look nothing like they did in the past. I think that is somewhat due to language features (annotations, lambdas, etc) but also due to a cultural shift in what is valued.

One of the things I've appreciated more than I would have expected is by having a single back-end language we have very strong community of developers. There is no split among different factions. (I hear rumors of sharp divides between python and node camps at Uber, for example.) Even though technically we have a platform capable of running languages in many languages, the value of the community focused on a single back-end language toolchain is extremely valuable.

HubSpot | Cambridge/Boston/Dublin | full time, onsite

Looking for front-end (React/Flux, Backbone, ES6/CoffeeScript) and back-end (Java8, HBase, Kafka, Hadoop/Spark, ElasticSearch) developers who enjoy working in small teams that own significant parts of our products. Developer autonomy and responsibility are what fuels our product culture. Our products are helping transform how small businesses do marketing & sales so they grow while delighting their customers.

The products we build help small businesses grow. More on our product team and roles on our site: http://product.hubspot.com/ and our company culture: http://culturecode.com

Or ping me (champion at hubspot) with any questions.

HubSpot | Cambridge/Boston/Dublin | full time, onsite

Looking for front-end (React/Flux, Backbone, ES6/CoffeeScript) and back-end (Java8, HBase, Kafka, Hadoop/Spark, ElasticSearch) developers who enjoy working in small teams that own significant parts of our products. Developer autonomy and responsibility are what fuels our product culture. Our products are helping transform how small businesses do marketing & sales so they grow while delighting their customers.

The products we build help small businesses grow. More on our product team and roles on our site: http://product.hubspot.com/ and our company culture: http://culturecode.com Or ping me (champion at hubspot) with any questions.

HubSpot | Cambridge/Boston/Dublin | full time, onsite

Looking for front-end (React/Flux, Backbone, ES6/CoffeeScript) and back-end (Java8, HBase, Kafka, Hadoop/Spark, ElasticSearch) developers who enjoy working in small teams that own significant parts of our products. Developer autonomy and responsibility are what fuels our product culture. Our products are helping transform how small businesses do marketing & sales so they grow while delighting their customers.

The products we build help small businesses grow. More on our product team and roles on our site: http://product.hubspot.com/ and our company culture: http://culturecode.com

Or ping me (champion at hubspot) with any questions.

HubSpot is hiring for software developers in Cambridge/Boston and Dublin ONSITE.

Looking for front-end (React/Flux, Backbone, ES6/CoffeeScript) and back-end (java, hbase, kafka, hadoop) developers who enjoy working in small teams that own significant parts of our products. Developer autonomy and responsibility are what fuels our product culture. Our marketing & sales platform help small businesses grow.

More on our team, culture and roles: http://product.hubspot.com/

Or ping me (champion at hubspot) with any questions.

HubSpot is hiring for software developers in Cambridge/Boston and Dublin.

Looking for front-end (React/Flux, Backbone, ES6/CoffeeScript) and back-end (java, hbase, kafka, hadoop) developers who enjoy working in small teams that own significant parts of our products.

Developer autonomy and responsibility are what fuels our product culture. Our marketing & sales platform help small businesses grow.

More on our team, culture and roles: http://product.hubspot.com/

HubSpot - Boston/Cambridge - http://product.hubspot.com

Looking for front-end developers (React, ES6, Backbone, CoffeeScript) or back-end developers (Java, Dropwizard, Kafka, Elastic Search). Position is onsite in our beautiful office.

We're building platforms for sales & marketing software. Each team owns a core vertical of the product, and are given real responsibility and ownership of their components.

HubSpot is hiring for software developers & designers in Cambridge/Boston and Dublin.

Looking for front-end (React, Backbone, ES6/CoffeeScript) and back-end (java, hbase, kafka, hadoop) developers who enjoy working in small teams that own significant parts of our products. Developer autonomy and responsibility are what fuels our product culture. Our marketing & sales platform help small businesses grow.

More on our team, culture and roles: http://product.hubspot.com/

PMs and designers work with one or more 3 person engineering team. Often times the PM/designer work across several engineering teams in 1 "family".

Personally I've been a fan as it aligns incentives for developers to care deeply about code quality/stability/etc. YMMV if not working on a SaaS product where build/deploy is measured in just a few minutes.

We've invested in a mix of both automated testing, of course, and a lot of monitoring/alerting/tracing to detect problems quickly. That can act as a safety net for deploying frequently that problems will be caught early and can be corrected (rollback or fix & roll-forward).

I'm a fan of saying we've chosen to optimize for MTTR instead of MTBF.

About 25 plus or minus.

I'm not sure how to best characterize it in the very beginning (and I wasn't there) but in the 3.5 years I've been here it has largely been smaller services -- even down to things like the app's nav is its own service. More recently I think we've really embraced microservices (the number of deployables has grown ~2x in the last year).

Personally I think after 5 (and definitely 10) engineers working on a single app I would look at whether you can break it down into independent services.

Saying RSUs tend to be better is potentially true (at least a higher expected value) since they are likely to be issued by public companies rather than early stage companies.

If you're doing well and the company is sensible they will continue to offer you additions equity grants so there isn't that incentive to leave as your compensation falls. This post describes the "evergreen" aspect to granting equity: http://firstround.com/article/the-right-way-to-grant-equity-...

Similar, I graduated with a BS in CS in 2001. I was lucky to have finished my job search in the Fall of 2000. The market had still been hot in the fall, I received several (4-5?) offers for 60-75k (boston/nyc). Each seemed like they were on the "new, exciting" project at a company where their revenue came from elsewhere. I took a job with a company I'd interned at.

By the Spring things had definitely changed. First lots of hiring freezes and then offers to friends rescinded. (A few lucky ones got paid 50% to take a year off.) I think most of the offers I had were for projects that were likely killed since they didn't add anything to the top line. The did a round of layoffs where I was joining in the spring before I started. I remember anxiously waiting at my college apt to find out if I was unlucky. I wasn't affected, I believe primarily because I was "cheap" compared to the people making 2x or more than me they chose to let go.

I felt very fortunate to land on an interesting team doing real product development; others I know who graduated in 2002 had no option but the longer path through customer support / non-tech jobs for a little bit.

I loved TechStars but the WSJ analysis seems flawed. Primarily because I think that data is stale (there are definitely zombie/dead companies counted as "active") and a category like "acquired" it too vague. The way it reads it seems like that was a good outcome (and for companies like Gradcad it was!) but many others it is basically acquihire.

There was a good conversation between Dave McClure and Sam Altman about value of the grand slams vs singles/doubles: http://www.youtube.com/watch?v=489JA4ERzUY

I'd put Localytics on that list as well.

Can't tell if this is a joke. Typical time to IPO is like 8+ years aka longer than TechStars has been around.

Liked this, and have found the same. That even those with well-read, respected blogs struggle like everyone else to know what is the right next move.

Not yet, although that is something we've heard from at least 1 other person who uses a similar system (that they manually do in Excel)

damn, they got CUTT

I have mixed feelings about it. I certainly think it is helpful to know when something with published for the context you mean. I think it also probably makes sense to lead less with it for content that isn't that time-sensitive.

The broader point is that I think people will organize their content less around timestamps and more around relevance, the reader, etc.

I ordered a polo as part of their Kickstarter launch and really like it!