ericclemmons

New management. There was a reorg (coup) where tech is actively excluded, yet still the target of blame.

I'm redoing that whole stack, as it was a prototype to get buy-in to "fix" the Webpack API for most cases.

For an eslint-style plugin system I'd recommend webpack-blocks.

In Node, I consistently reach for Knex, which is less of an ORM (like Bookshelf) and more like a query builder.

This simplifies binding, mapping, and most queries.

There have been rare situations to use ".raw", but the escape hatch id there.

As a hiring manager, I used to want to see a profile that competed with my own (at the time).

Now I've learned that (1) burnout is real, (2) work CAN be intellectually stimulating enough to not create that OSS desire, and (3) eventually your job ends at 5 and life takes over.

With that said, I WISH more developers opened issues on the projects they've used.

All too often I've seen people drop one dependency for another due to an edge-case.

Even a simple issue explaining the problem, providing a test case or sample code would be great as an indicator to how a developer approaches problems and seeks help.

As a parent, appropriate is determined by my children's ability to yield the knowledge correctly.

Take swears for instance. Until they know better, there's more risk of them using swears at the wrong time.

What's exciting to me, having tested graph.cool and others, they are fantastic at providing an API in a format that works quite well (GraphQL) and handing the admin for me.

I don't want to build admin anymore.

Frankly, I'll spend more money at the service with the best admin UX.

It's like MixPanel for analytics. I can perform complex queries and analysis with minimal friction, which makes it worth the cost.

"Owning" isn't a selling point for me, when all of the services make it possible to dump the data.

Outside of work hours, as long as it doesn't compete it's yours.

Once kids are in bed, it's Overwatch time.

I've struggled with helping people out of this rut.

On the tech side, people come to me with solutions they want to see live, and spend 10x the time there than describing the root problem.

Equally important is asking "why not" to alternative scenarios, as it fleshed out the scope of the root problem, often vetting the initial solution or finding a better one.

If you want a pretty terse way of defining a GraphQL API, Apollo works very well (with mocking, too).

The UX is top notch. Not only is the UI polished, but big details like mentioning someone and an invite link appearing is awesome. Or force-pinging someone on DnD because of an emergency.

Slack is seriously user-centric, all the way down to how they run their Twitter.