So I’m a big fan of Tailwind. I think the framework makes CSS grok-able again by providing a subset of the language that has been mostly well-thought out, but still has enough escape hatches so you can do anything CSS can do (mostly)—without writing CSS.
Because Tailwind is so flexible and open-ended though, it’s hard to get started with a more complete layout, part of the reason why Tailwind UI—a component framework that built on top of Tailwind, and by the original creators—sold so well. We ended up purchasing Tailwind UI at Lucideus at the last project I worked on just for this reason: to give a new team more experience with how to build with Tailwind.
Well now, we have an open source alternative: Tailblocks.
Tailblocks seems to be focusing mostly on more fully-fledged layouts now, compared to Tailwind UI that provides more granular components:
But nevertheless, this is really good news. More libraries and code examples for Tailwind—for free—never will hurt 🙂
I think all of these are valuable, but perhaps a few can be clubbed together. I had these 8 criteria when I was job hunting:
Product: Product company, not services or a software consultancy. Simply because products matter. There’s a good Steve Jobs video as to why!
Bootstrapped/Public: Not stuck at going after growth for VC’s sake. Venture capital is great for most companies, but I’ve rarely seen it have the right indicators to build the kind of product I want to contribute to: those with long-term, lasting value, and simple economics.
Profitable: Ideally a profitable SaaS or other company that is making money. Profitable companies are just great. It’s again the simplicity of the economics that appeals: there’s no hockey-stick growth required: you spend less than you make, and you save for a rainy day.
Salary: Pays within 10% of top-of-market. I think Software Engineering is enough of an in-demand skill that if you are good, this should be a given.
Remote: Is primarily remote (truly remote, not just US) or has a good remote-working culture. The truly remote also includes asynchronous communication.
Open Source: Has significant open source contributions. Two reasons, one: because most often stewarding a good open source community looks a lot like building a good remote company. And the next, giving back starts at home.
Interviews: Has a sensible interviewing process with a take-home test. I despise the whiteboard interview. It’s much harder to be a company that executes the alternative—a take home test—but it’s much more humane and respectful.
Balance: Respects personal time. Allows for at least 20 days of vacation in a year. This should be self obvious. Taking downtime is as important as work.
Make your criteria before you start a job hunt. But People-First jobs is definitely a good place to start.
This really spoke to me for the simple reason that so many, many times, I’ve started projects only to abandon them halfway simply because it wasn’t good enough. Recently, I’ve convinced myself to finish by saying: “It’ll never be good enough.” But: this video put a much more positive spin to it.
Recently came across tsdx and ported over a small library at Doist to it. It’s a really cool way to get started with building a Typescript library. Jared Palmer is the same dude who built Razzle & Formik, 2 great projects that I’ve used before to great success 🙂