epberry

I work on what you might call a 'database IDE' and we have actually gone in the opposite direction, adding more features for offline development and maintaining state offline. We were pretty open either way but our users pulled us this way. Interestingly I think the enterprise may be more open to this remote environment thing, as long as it operates within their network.

> Oso’s Django and SQLAlchemy integrations turn partials from Polar into database queries... The SQL they produce relies heavily on nested subqueries

Live by ORM, die by ORM. This strikes me as particularly bad because these authorization queries may be running on every request. It's great to see Oso went direct to SQL to address this. And the asides about logical programming were fun as well.

How can you not think this is great? Freeing humans from menial tasks is the way forward. Remember when people (mostly women) would spend hours washing? Machines and automation freed them.

The referential integrity piece (otherwise known as Foreign Keys) will not be addressed and is a limitation - some might say feature - of Vitess. They wrote a pretty good piece about it here, https://docs.planetscale.com/tutorials/operating-without-for...

I'm developing the open software stack for cashierless checkout systems at http://prcvlabs.org

More generally I'm interested in continuing to study large scale computer vision projects. Progress has been slow with a new job but I'm hoping to gain momentum through the winter.

I think the hybrid model is just because of inertia. Working fully remote will be the norm for most software companies. Not sure about other industries.

jsonb has become the crutch on which I build everything. And I'm not going back.

You have to place JVN in his time on this issue. If you were a person with first hand knowledge of the atomic weapons program, access to the highest levels of national security, and a normal person's view of foreign policy (as in you were not a diplomat or experienced on the world stage) it's a coin flip whether you would have argued for restraint or first strike.

I've been learning about the Dulles brothers recently and the most hawkish Americans of this time period were a lot more hawkish than the neocons of today. I am very glad that cooler heads prevailed but I don't know that it should be such a knock on his reputation that he was in a different camp.

I've seen a lot of posts analyzing HN content. This would be a very interesting topic.

I agree. https://github.com/jonls/redshift has been a gamechanger to me. Hint for those with desktops: redshift may fail to detect your location so you can use -l lat:long to set it.

This is the best of the hacking world. For me, small platforms that are open and require careful memory management are what computers are all about. Maybe it's because my day to day involves effectively unconstrained resources and massive systems that are slow until they're too slow and then they get fixed.

Fascinating to see the focus on SQL and continuous integration, https://docs.sqlfluff.com/en/stable/inthewild.html#inthewild.... DBT has really changed things in that regard. @tomhallett's YT video seems to describe using this with a pre-release build of DBT to tightly couple it to sqlfluff.

Been a timescale user for a little while and here's how this is different than their previous offering:

- Scale compute or storage separately

- One click spin up, pause, and recover

- Configure data retention (docs page not complete)

- Set a refresh policy for continuous aggregates via web console

- One click VPC

There's other stuff in that list but I either didn't miss it in the old Timescale or don't use it. Overall continuing the coupling of dba and analyst/backend dev via software. A nice set of changes.

What company size and deployment model would make maintaining this worth it? 50 engineers and daily builds? I know there are much more complex systems in big tech where you would want a lot of control over the CI process. I assume this is for a mid market or even small company.

Looks pretty nice. The codebase is half typescript and half Java? Guessing that is because Kafka is written in Java.

Another question: how might this compare to the Confluent web GUI? Obviously this is open source which is great.

Interesting architecture for sure to create a partial index every time a user creates a new event. One question I have that wasn't clear: how fast is that event queryable by the user after it is created? It sounds like there is a redis queue that manages the creation of the indexes and I imagine that takes some time to work through.

Exciting stuff, congrats. One note, the sponsor link on PyFilesystem is broken, https://github.com/PyFilesystem/pyfilesystem2

5X on count distinct is definitely good. The base dataset is 10M rows it looks like. The fact that this tool exists and has 3.5K stars on github is an indictment of the difficulty of getting started with hosted dbs, while also a wink to the current speed of broadband and power of memory in desktop machines now.

Very thorough tutorial, although as the conclusion says this code works for this specific environment and would not adapt to new ones. Ofc it's only 500 lines :)

This is pretty useful and annoying to get right across multiple web properties. Nice work!

Psssst https://calendso.com/

South Korea is not 100 miles from China and has a massive US military presence. This article is about the very real danger that China invades Taiwan - which it has already stated it wants to do (in case the military flyovers were not convincing) - and cuts off the world from the best silicon.

Credit to these guys for not giving up. Hiring engineers remains unsolved so if they're still in the game they still have a chance to ultimately solve it and reap the rewards.

Are you calling Sam Altman a one trick pony? Quick list of his "tricks": - founded company, raised $40M - proved YC can scale - numerous strong individual investments (Humanyze, Routable) - CEO of OpenAI leading to $1B investment from Microsoft

If allocating capital well makes someone a one trick pony, then I think we need many more ponies in the world.

This will get you started but is by no means a full guide on query optimization, https://arctype.com/blog/postgresql-query-plan-anatomy/. There's also a fair number of django posts on this blog.

We should all be grateful that Senator Wyden has been a champion for these issues. I like to watch him in hearings and it's clear he's one of the most well prepared questioners on issues of privacy and liberty. To the staff of his office, if you're seeing this comment section - thank you!

The coroutine syntax is actually quite nice.

Arctype | Senior Software Engineer | Full Time | REMOTE At Arctype, we're building the best collaborative SQL client for PostgreSQL and MySQL. We are backed by Social Capital and Chamath Palihapitiya, and other great angels.

Arctype is looking for a founding software engineer interested in building a truly great SQL client. We're a team of engineers who have worked at cutting-edge startups and enterprises. After struggling with terrible query interfaces at every job, we set out to build a best-in-class SQL client with built-in collaboration, version history, sharing, and more!

As a software engineer at Arctype you will work on every part of the product, from the database connectors to our visualization tools, to our SQL language parsers. You'll get to chat with users every week and see your changes go live and have an impact. Feature suggestions and product breakthroughs come from everywhere. At Arctype, if you can dream it you can build it (as long as users love it!). Compensation for this role includes a competitive salary, equity befitting an early-stage employee, and benefits.

Required Skills: Javascript, React, Node, Git, SQL

Nice to Have: Cool projects, Figma, CSS

Email: jobs@arctype.com

Tryout https://arctype.com it’s a free SQL editor for devs. Closed source but it has a fast interface and good aesthetics. i started using it at my previous company with a team of 4.

Can you talk about the experience of starting to maintain it and gain acceptance for new commits from debian upstream? I've got my eye on a few little pieces of software to start working on but am afraid to make the leap.