daigoba66
daigoba66 on Hacker News
Posted by
daigoba66 on Wednesday September 30, 2026 @04:37PM
from the aws.amazon.com dept.
I’ve noticed this trend on LinkedIn just recently. Very noticeable at night, obviously, when my screen is naturally more dim. But these logos are like blinding headlights.
Posted by
daigoba66 on Thursday April 02, 2026 @11:35AM
from the arxiv.org dept.
FWIW, I think that’s essentially how Aurora DSQL works, and sort of explained at the end of the article.
> I really wish there were a de facto state-of-the-art coding agent that is LLM-agnostic
Cursor?
It’s really quite good.
Ironically it has its own LLM now, https://cursor.com/blog/composer, so it’s sort of going the other way.
Posted by
daigoba66 on Wednesday October 01, 2025 @06:10PM
from the devblogs.microsoft.com dept.
Posted by
daigoba66 on Thursday May 08, 2025 @11:51AM
from the newsletter.techworld-with-milan.com dept.
Posted by
daigoba66 on Thursday February 06, 2025 @04:26PM
from the devblogs.microsoft.com dept.
Posted by
daigoba66 on Tuesday December 03, 2024 @01:29PM
from the brooker.co.za dept.
Posted by
daigoba66 on Monday July 29, 2024 @02:59PM
from the brooker.co.za dept.
Posted by
daigoba66 on Saturday February 17, 2024 @05:05PM
from the shekhargulati.com dept.
Posted by
daigoba66 on Friday December 01, 2023 @07:23AM
from the youtube.com dept.
Posted by
daigoba66 on Monday November 27, 2023 @11:57PM
from the aws.amazon.com dept.
> One best practice that I'd love to see spread (in our codebases too) is always naming the full feature flag directly in code, as a string (not a constant).
Can you elaborate on this? As a programmer, I would think that using something like a constant would help us find references and ensure all usage of the flag is removed when the constant is removed.
As an aside, those “feature flags as a service” tools have some neat features, but are just way too expensive for what most apps probably need: simple binary flags that can change at runtime.
Example: just use a database table. Query and cache in memory for 60s. If you want, build a simple internal web page or tool to toggle flags. This works, and scales (from experience).
Do many apps really need A/B testing or segmented rollout? Maybe, but probably not.
Isn’t that functionally the same as “ignore dots”?
Meaning they can just strip out the dots when matching email addresses: either on login/signup or mail routing.
You’re probably thinking of debug symbols, i.e. the PDB file that is generated alongside the binary. You can generate this for both Debug and Release builds (should be on by default in fact). It’s super useful for debugging crash dumps from production, and for exception logging in web apps.
You can think of this like a source map, but only files and line numbers.
Another common spot to easily find Megalodon and other large shark teeth is the Savannah River just past the shipping ports. The river dredging from a few years ago created a few new “islands” where shark teeth are plentiful.
> what's going on here and how every single website has this new slowness
Everyone and everything uses OAuth/OIDC.
And as long as you never rename the departments.
This is basically my own experience as well.
How do you distinguish what is "layout" versus "style"?
I know there are some obvious things, but like you said CSS is used for both. So there is a lot "grey area". Especially when "style" can affect the "layout".
Maybe funny 4-5 years ago, but these days it’s incredibly well supported across Windows/Linux/MacOS.
Posted by
daigoba66 on Friday August 26, 2022 @08:13PM
from the devblogs.microsoft.com dept.
I’ve been told that spiders can be beneficial for getting rid of (i.e. eating) other pests - actual insects. Obviously if I find a spider in my living space, I’ll relocate it outside. Since almost spiders, in the US, are virtually harmless, they’re pretty easy to move with a cup/tissue/paper/whatever.
Posted by
daigoba66 on Wednesday July 27, 2022 @09:48PM
from the shekhargulati.com dept.
Coming from an MS SQL Server background, this behavior surprised me.
While SQL Server generally does treat null values as not equal in query predicates, for the purpose of unique constraints/indexes it’ll treat them as the same value. I guess this does go against the spec? But it makes sense as a human when looking at a tuple and deciding if it is “unique” or not.
On that note, now I wonder what SQL Server does with nulls in a DISTINCT or GROUP BY. I suspect that it’ll treat all nulls as the same.