1719
submitted 10 months ago by tsuica@lemmy.world to c/programmerhumor@lemmy.ml
you are viewing a single comment's thread
view the rest of the comments
[-] AlexWIWA@lemmy.ml 10 points 10 months ago

Timeout was the wrong word. It has to be held for like a quarter second or something like that. It's annoying as hell.

[-] icedterminal@lemmy.world 8 points 10 months ago
[-] AlexWIWA@lemmy.ml 4 points 10 months ago

Yeah it's even worse when you remote in to a windows machine from a Mac. It has the caps lock annoyance and then the delay on the remote machine will cause the first keystroke after toggling caps lock to not actually know that it needs to toggle, so your sql looks like this sELECT * FROM Table_name tn wHERE Tn.thing = tRUE

[-] curiousaur@reddthat.com 2 points 10 months ago

What? Mine doesn't do that. I've been using Mac's since 2016 when I learned to code, and I've never seen this behavior.

[-] icedterminal@lemmy.world 5 points 10 months ago* (last edited 10 months ago)
[-] AlexWIWA@lemmy.ml 2 points 10 months ago

It definitely exists. It's far more noticable if you plug a keyboard into your MacBook. There are threads all over Mac forums and stack exchange asking how to disable it.

[-] curiousaur@reddthat.com 2 points 10 months ago* (last edited 10 months ago)

I use an external mechanical keyboard exclusively.

Ok, just went to my work machine and I guess you're right. If you hit the caps lock key quickly it doesn't register. Don't know why I never noticed, I am a software engineer. The ai writes all my SQL now though, so...

[-] AlexWIWA@lemmy.ml 2 points 10 months ago* (last edited 10 months ago)

Then be happy you naturally hit the caps lock key slowly enough to have never noticed this. When flipping back and forth between caps lock in SQL it drives me up the wall.

https://www.reddit.com/r/macbook/comments/o6q52c/mba_m1_caps_lock_key_delay/

To be clear though, I never noticed either until I started writing SQL regularly. It never causes me problems when writing regular code

[-] curiousaur@reddthat.com -3 points 10 months ago

Seriously though, why are you writing your own SQL still? It's the language LLMs are the most accurate at translating English into. Like, the most insane inline aggregation, nested transaction nonsense; it just does it for you if you describe what you want and it knows your schema.

[-] AlexWIWA@lemmy.ml 5 points 10 months ago

It doesn't know the schema nor can it due to the sensitivity of the data I work with. It's also faster to write the SQL than to describe it to the LLM. Once you get used to it, SQL is easier than English.

[-] curiousaur@reddthat.com -1 points 10 months ago

You can keep it private. And if you think you're better than it you haven't tried it. You can name the statement, and it will figure out what you want.

[-] xmunk@sh.itjust.works 2 points 10 months ago

It depends on the SQL. Anything non-trivial is still much better to write by hand to keep the intent clear.

this post was submitted on 19 Oct 2023
1719 points (98.8% liked)

Programmer Humor

31700 readers
763 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS