leftnode

Excellent article, thanks for writing and posting it.

A little harsh, no? Damn dude.

I instantly purchased this. I really love Tailwind and the component/UI libraries they sell. I'm shocked that a CSS library/framework is so divisive. If you don't like it, don't use it!

I'm also surprised that someone ... selling something ... gets such negativity on Hacker News of all places. Again, if you don't like it or it doesn't have value to you, don't buy it!

I paid for it because I love what Adam and team are doing with Tailwind. It's been incredibly beneficial to use as a backend engineer, and the amount of money paid is trivial to the benefits it provides.

Is it widely assumed the thief is North Korea?

Additionally, I'd wager a good majority of their paying customers had no idea the controversy was happening, or weren't going to change their entire office operating procedures because the owners may have some caustic opinions.

Brazilian Jiu Jitsu - It's an odd combination of intense physical activity and human chess (setting up attacks in advance while also trying to deflect your opponents attacks, except using chokes or joint breaks). Grapplers are either freak athletes, 120lb stoners, or business professionals. BJJ is one of the most unique sports/martial arts out there, and I encourage everyone to try it at least once.

I started after enrolling my children in it, and then figuring "why the hell not, I should train too."

This seems shortsighted. There are dozens of reasons you may want to get to know your neighbors: help each other out, become friends, watch a package, babysit, petsit, and so forth. Sure, nothing may happen from an interaction, but it seems one of the unique aspects of living in an apartment complex is that you can easily know your neighbors.

I live in a large neighborhood of single-family homes and know many of my neighbors, most of which have become good, trusted friends.

I agree. From his site it appears he's a "coach" that some executive hires to hold an all hands team building exercise that the rank-and-file completely dread. No thanks.

That's exactly what we do: submitting a search/filter form through a POST request which creates a record in the database representing the search/filter criteria and then redirects to the same endpoint with the ID of that record. The endpoint looks for the ID in the query, attempts to load the same record, and if found, executes and returns the search results.

It works very well, is completely transparent to the end user, has automatic query logging, and provides a clean URL that can be easily shared.

Great to hear some people still follow the KISS method. I've done the same for years and this very simple setup can scale to tens of millions of (database intensive) requests per week.

Home service businesses (contractors, electricians, plumbers, HVAC, roofers, etc). Even houses owned by banks/investment groups need repairs done. It's a huge industry that desperately needs employees.

Not the OP, but also selling B2B software. You can hold a user accountable that they'll actually use the software purchased. The company is spending a lot of money on it, finds value in it, and wants to ensure it's being used and implemented correctly.

B2B software with figures like the OP means you're building a professional relationship with a customer (as opposed to a transactional one), and can push back when they're complaining about something, for example.

> "Your software isn't giving us the numbers you said it would!"

> "It will, if you use it as you were instructed, we're happy to review that with you again, but you have to have the internal SOP that you'll use it in the way it was intended if you want the numbers it can provide."

Perhaps you could extend the Pipe class and thus the pipe() method returns an object for chainability? That's the only reason I can immediately think of.

"Senior" developers tend to waaaaaay overestimate their abilities, unfortunately.

Absolutely amazing project, happy paying customer.

As a developer and business owner, I literally can't comprehend this response. I can't imagine idea of having to manage yet another server over running

    ngrok http 8000 -subdomain=my-custom-subdomain

from the root of my application (which is wrapped in a single line shell script). For a business, paying $10/dev/month for ngrok is a rounding error.

You can generally get good, inexpensive Irish butter at Costco in America easily.

There's a piece of software (that I have no affiliation with) that has a feature like this built in named Guru: https://www.getguru.com

This is great. Thanks for maintaining this artifact of pre-Web 2.0 days. And who knows, the next hot startup Jubyla may want to buy the domain for millions.

It is, and something an ORM can manage, but I spend a LOT of time in the psql CLI.

That's generally what I end up doing. It's not ideal, but it at least allows me to order the columns how I want.

I love, love, love Postgres! The one feature MySQL has that Postgres doesn't is the ability to add a new column in an arbitrary position in the table. I like my tables to have a common "layout" and I would love to have this feature in Postgres.

I regularly deal with JSON documents several MB in size, but do developers frequently deal with JSON documents several GB in size? If so, where do you encounter something like that? Surely "processing" that much data (for whatever definition of process you have) is orders of magnitude slower than parsing it.

I love the idea of a library trying to squeeze every last bit of performance out of the CPU, but I'm genuinely curious at the problems it solves in the real world.

The impact Vagrant has had on my business is nearly immeasurable (and for free, no less). We're a small startup, and I haven't had the time (or motivation) to learn what Docker, Kubernetes, containers, etc are. Seems overly complex.

But, virtual servers I can understand. I've been using Vagrant since 2013 and it ... just works. We've built our own custom box to standardize our development environment as well.

If there is one company and person I'd like to mimic, it's Hashicorp and Mitchell. Work to build an amazing product or products, get it ready for a sale or IPO, and then transition into an IC to continue doing what I love: hacking.

Congratulations on the success!

Congrats on the launch. Unrelated to the actual software, are any of you actual Jiu-Jitsu grapplers? If not, why'd you go with the name Jitsu?

Surely Substack uses Amazon SES or another transactional email service to actually send the emails to their user's subscribers, right?

It also helps spread knowledge around so more than one person has knowledge of a new feature, bug fix, or sub-system.

Another added benefit is that you can build a simple interface to allow end users to adjust their sequences (or our support staff in this instance).

In our system, by default, all objects start at 1000. If a new account is created, and they want to increase a sequence to some value (say they already have 5000 invoices in QuickBooks and they want to start all new invoices at 10000 so they know every invoice #IN10000 and higher was created in our system), we have a simple interface that one of our support staff can go to arbitrarily increase the next value.

We have a similar system (multi-tenant database) where each tenant (account) has objects that have unique identifiers for that specific account (customers, locations, jobs, invoices, etc).

Customer #C1010 may have 2 locations #L1899 and #L8443 and many invoices #IN1940 and #IN2399 for example.

When we first built the system, I considered using native Postgres sequences to track these, but decided against them because of how they are affected during a rollback. In our system, each account has a record in a table that controls the next value of the sequence.

We have an event in our ORM to automatically generate the next sequence value as part of the transaction so if the transaction is rolled back, the next sequence value is as well. Sure, it requires locking the sequence record but it's a very small table and generating a sequence is quick. We wrapped everything up in a stored procedure named generate_sequence() which returns the next value of the sequence and increments it. It's scaled to millions of records quite well without issue.