CRAIG KERSTIENS

I recall extremely early stage where you’d build a feature, realize it was awesome, then the next day write a blog post for it.

JSONB in Postgres is absolutely awesome, but it’s taken a little while for libraries to come around to make it as useful as would be ideal.

First some background–I’ve always had a bit of a love hate relationship with ORMs.

These days if you’re creating a company you likely hope to accomplish more with less people, two ways of doing this fall to: The sharing economy and creating a platform.

When it comes to go to market and marketing there’s lots of pieces in a toolchest that all work together.

You’ve built your product and you’re now ready for your first major launch.

Often when you’re tracking a metric for the first time you take a look at your average.

If you’ve followed anything I’ve written about Postgres, you know that I’m a fan.

I find myself having more conversations with startups – both small and large – about product management.

Most web applications will add/remove columns over time.

As I followed along with the 9.4 release of Postgres I had a few posts of things that I was excited about, some things that missed, and a bit of a wrap-up.

A few weeks ago at lunch I had the opportunity to catch up with a company in the current YC batch, building something very similar to dataclips.

In the process of growing a company there’s several hurdles based on the size of the company.

Connection pooling is quickly becoming one of the more frequent questions I hear.

If one of the industry lingo terms in title didn’t make your skin crawl a little then I need to try harder.

Postgres has a variety of datatypes, in fact quite a few more than most other databases.

Yahoo Amazon.com Netflix Various banks Many more If you’re interested in more technical details you can follow along or on the Heroku blog.

Marketing is generally unexciting to a ton of engineers, until it brings eyeballs which bring feedback and dollars.

A couple years back I started more regularly blogging, though I’ve done this off and on before, this time I kept some regularity.

Just a few weeks back I wrote a article discussing many of the things that were likely to miss making the 9.4 PostgreSQL release.

In analyzing a business I commonly look at reports that have two lenses, one is by doing various cohort analysis.

Theres no doubt that the 9.4 release of PostgreSQL will have some great improvements.

In a conversation with @alexbaldwin yesterday the topic of email came up, with each of us quickly diving into various observations, how its both awesome and a great form of communication/engagement, how most people still do it really bad.

PostgreSQL is currently entering its final commit fest.

Last week I wrote up some initial steps for getting started with marketing a developer focused product.

Theres a lot of back and forth on NoSQL databases.

Getting the word out Hacker News When it comes to marketing, specifically to developers, the most common question is how do I get on Hacker News?

Commonly at developer focused companies the question from a marketing team will come up of “How do we get content that developers find interesting”?

I wrote a couple months back about exploring FDWs.

SQL by default isn’t typically friendly to dive into, and especially so if you’re reading someone else’s already created queries.

Emails are one of my favorite methods of communicating with users.

Google hangouts is awesome, its my preferred method for most audio/video calls these days.

Just as PostgreSQL 9.3 was coming out I had a need to take advantage of the JSON datatype and some of the operators and functions within it.

Several months back I wrote about how we do higher level, long term planning within the Heroku Postgres team.

For a couple of years I’ve complained about the Postgres documentation and at the same time paraded it as one of the best sets of documentation I’ve encountered.

There are two particular sets of features that continue to keep me very excited about the momentum of Postgres.

After my most recent post on documenting your database I had a colleague and friend chime in: {% blockquote @danfarina https://twitter.com/danfarina/status/362007008079126528 %} @craigkerstiens You may want to mention for another post the generality of do…

Just a few days ago I was surprised by what someone was doing with their database, and not in the typical horrifying travesty against mankind.

If you’re deciding what to put in Postgres and what not to, consider that Postgres can be a perfectly good schema-less database.

Earlier today on an internal Heroku group alias there was a dataclip shared.

Javascript in Postgres has gotten a good bit of love lately, part of that is from Heroku Postgres recently adding support for Javascript and part from a variety of people championing the power of it such as @leinweber (Embracing the web with JSON and PLV8)

I’ve written a bit before about understanding the output from EXPLAIN and EXPLAIN ANALYZE in PostgreSQL.

Even from intial reviews of my previous post on expression based indexes I received a lot of questions and feedback around many different parts of indexing in Postgres.

Postgres is rich with options for indexing.

I’m reasonably proficient at SQL – a coworker when pseudocoding some logic for him pointed out that my pseudocode is what he thought was executable SQL.

Following up on my earlier post about CX or Conference Experience – I’m going to dig in a bit on getting the right people there.

Following up on my earlier post about CX or Conference Experience – I’m going to dig in a bit on how you get good conversation to happen.

A couple of weekends ago I had the great opportunity to attend lessconf.

Just over two years ago, Heroku was acquired.

In almost any application it’s common to want to aggregate some set of values together, commonly in a comma separated form.