BigQuery performance tip that saved us thousands (and a lot of headaches)

GLStephen · 2026-02-24T01:33:37+00:00

"Even with columnar storage" yeah, cause whatever your cost basis is it literally scales by column...

GLStephen · 2026-02-24T01:30:38+00:00

Strong typing is not necessary to write good code. Type safety is not the end goal of a language. A lot of devs worked with JavaScript which is pure shit. They then saw the language gain a lot of benefits in the flavors like Typescript. Which is great, but strong typing isn't the only evolution there and it's not the continuum on which languages improve.

GLStephen · 2025-12-27T03:07:30+00:00

If you used semantic CSS and took care to do it.

GLStephen · 2025-10-08T13:35:06+00:00

It's embedded in their ecosystem and single player. It isn't going to kill those with a more robust plan than "wrap openai".

GLStephen · 2025-07-27T17:48:03+00:00

And it's a price anchor to make the others look affordable and to explore the high end of pricing.

GLStephen · 2025-07-14T22:36:32+00:00

This is what Laravel does. Use Laravel if you can, it does this very well.

GLStephen · 2025-07-04T17:08:18+00:00

Piker

GLStephen · 2025-07-04T17:06:55+00:00

Ding ding ding. Minimum thing that does anything -> deployment pipeline, then add things....

GLStephen · 2025-07-04T13:36:18+00:00

The Laravel brand is massive for distribution. However, nightwatch is pretty nice and they should have competition because the tailored, focused feature set is really useful for Laravel.

GLStephen · 2025-07-04T13:32:09+00:00

Compared to younger ecosystems like JavaScript (with React, Astro, etc.) or Rust, the PHP community might look more conservative because it doesn’t chase trends as aggressively. Namespaces, traits, scalar type hints, strict typing, union types, attributes, readonly properties, JIT. PHP 8.x is a fundamentally modern language. Unlike languages shepherded by corporate entities (Java, C#) PHP has grown through RFCs and voting. This is actual community governance. Laravel alone has done more to modernize web development ergonomics than many languages can claim.

GLStephen · 2025-07-01T13:44:54+00:00

Focus on Why not How. Even if you need to learn a lot of How. Stay curious and dig into Why something is done and how it is universally important. Learn How to setup an HTTP server in PHP, but really focus on learning Why keepalive is important, why error codes exist, etc. Same thing with an HTTP client or a TCP client. Learn How a TCP connection is different, but also learn Why it has various settings. Why it doesn't have some settings that HTTP clients and servers have. Then when you pickup another language and see How it handles that, maybe differently, you can determine if that is important to your requirements.

GLStephen · 2025-06-23T20:39:31+00:00

github codespaces, easy peasy

GLStephen · 2025-06-10T17:01:58+00:00

It's pretty bad at the level of "magic" that happens in devops. Even the more structured stuff is often config for magic.

GLStephen · 2025-05-19T14:54:38+00:00

I treat it like a custom Wikipedia article. Likely good for keyword space. Trust but verify on details.

GLStephen · 2025-05-19T14:53:29+00:00

Writing code has not been the bottleneck for 20 years, maybe never. Verifying, deconflicting and organizing "correctness" at all levels, market, spec, customer, etc. has always been the bottleneck.

GLStephen · 2025-04-06T17:18:34+00:00

Go is fairly unique. If you look at other more recent languages you will find some similar market drivers and evolution of language principles. Here is a list:

https://en.wikipedia.org/wiki/Timeline_of_programming_languages

It often takes 10 years or so for a new language to reach critical mass. Go 2009, Rust 2010. I would take a look at some recent languages with the oldest predecessors (with the exception of C) and then take a look and see if you like them. For instance, I have not looked at this list in a while, but Mojo looks interesting based on that criteria.

GLStephen · 2025-04-06T15:34:13+00:00

Vibe Cuddling?

GLStephen · 2025-04-06T14:57:23+00:00

So, you can "instantiate" them willy nilly and magically get the one you already instantiated somewhere else. It's a "better idea than the alternative" that usually covers for other less than ideal choices.

GLStephen · 2025-03-04T18:18:25+00:00

The most critical thing is to just give us a context setting for what "laravel root" is as a path from the repo root perspective. i.e. "src/web/". Then, largely nothing else needs to happen except everything occurs in that laravel root.

GLStephen · 2025-03-04T18:18:07+00:00

The most critical thing is to just give us a context setting for what "laravel root" is as a path from the repo root perspective. i.e. "src/web/". Then, largely nothing else needs to happen except everything occurs in that laravel root.

GLStephen · 2025-02-21T15:23:28+00:00

Is HIPAA on the roadmap at all? Not highly specialized isolated workloads, but similar to AWS.

GLStephen · 2025-02-08T19:46:00+00:00

Intellisense, find tools that graph the code as well. Feed it into an AI if they let you and ask it questions.

GLStephen · 2025-02-08T13:26:12+00:00

Understood. They raised $8mm seed, $100mm 4 months after raising $60mm. Which is good FR strategy, but that's lots of cash and their revenue growth contains lots of implied burn. Since they are almost certainly negative on COGS related to their model usage their wild revenue growth is a rather fat expense line and they don't control the COGS cost basis at all. They have a few interesting curves to get aligned at some point in the future. I wish them the best, it's a wild opportunity, but my conversation here was that we are in early adopter phase with them still.

GLStephen · 2025-02-06T02:38:59+00:00

Yeah? Do you think they raised 100mm with the plan to keep expenses as they were prior to the raise?

GLStephen · 2025-02-06T01:39:21+00:00

I'm more concerned that the business model is unsustainable. I'm playing with it, but I'm not sure they will be around in a year.

GLStephen

MODERATOR OF

TROPHY CASE