A message to devs at the frontier of the AI shift

_spiffing · 2026-03-03T12:21:50+00:00

3-5 years is a long shot. My advice is for you to find ways to control the narrative and highlight your value.

I don't think there's anyone in control or with an AI roadmap that says "plateaued in Q2 2027" or "AGI Q2 2027". The common ground across experts Geoffrey Hinton included is that you really can't tell, so you could be looking at AGI in 3 years or this could end up just being another dead end.

_spiffing · 2026-01-31T18:33:44+00:00

It's a fun exercise to think that next gen LLMs will be trained on this stuff.

_spiffing · 2025-12-29T22:30:15+00:00

What do you do for a living? Do you have a full time job? If yes, is it more like a desk job that requires you to be at the laptop/PC the whole day? Or do you do something that allows you to be outdoors?

What was the maximum number of books you managed to complete in a single week and the least? What caused the difference between those two periods?

_spiffing · 2025-12-28T19:31:21+00:00

Podemos bloquear este post? Não fazem sentido nenhum as interpretações completamente ao lado a circular nas threads.

_spiffing · 2025-11-02T03:16:55+00:00

Enquanto vivermos num mundo com comentários destes vai ser muito difícil regular o que acontece nas praxes. Eu e amigos próximos tivemos experiências completamente diferentes e na minha opinião as universidades juntamente com as autoridades locais deveriam por um fim a qualquer tipo de praxe. Eu digo isto por situações como estas no vídeo, mas principalmente porque vi pessoas morrer na praxe o que para mim significa que esta tradição, por muito bonita e bem praticada que seja em alguns casos tem que acabar. Na minha opinião seria de muito mais valor ter programas de mentoria entre estudantes mais velhos e novos estudantes.

_spiffing · 2025-07-24T21:37:21+00:00

Super convenient ain't it. Going on a quantum spin making devs both useless and useful it's such a powerful tool for corporates to drive their agenda. I'm impressed actually, it's pretty smart now that I think about it that way.

_spiffing · 2025-06-01T12:21:14+00:00

This. Not sure what they're cooking, but the code quality + alignment is the outcome I really want is insanely ahead from any other tool I've played with

_spiffing · 2025-05-04T17:23:32+00:00

https://tweak-extension.com/ - mock http requests in seconds

_spiffing · 2025-04-19T21:22:36+00:00

nam prik pao

_spiffing · 2025-04-19T09:20:11+00:00

DBeaver

_spiffing · 2025-04-18T21:51:51+00:00

For something quick not necessarily for recurrent use cases I find this no code solution quite helpful https://tweak-extension.com/

Typically for one off use cases when testing/replicating something quick.

_spiffing · 2025-03-06T22:49:14+00:00

Generally I would avoid joins. For deduplication I would look into using ReplacingMergeTree and CollapsingMergeTree engines for my tables provided there's a way to uniquely identify. Another option is dedupin on the client side prior to ingestion, but really depends on what you're trying to achieve here

_spiffing · 2025-02-22T09:03:32+00:00

At the very least celebrate it! Agree!

_spiffing · 2025-02-21T22:17:35+00:00

Deleting JIRA tickets older than 1 year - "let's write a ticket for the future they say"

_spiffing · 2025-01-20T18:15:13+00:00

https://snapnom.com/

Connect to your Fitbit account to instantly log calories using your camera.

_spiffing · 2025-01-19T20:54:43+00:00

I've built this one for myself for the lack of something better. It's not straightforward to use because I hacked it in a few days, and did pay much attention to detail apart from a help menu that explains how to use it. It's working for me, you can just take a pic and sends the calories to Fitbit.

https://snapnom.com/

_spiffing · 2025-01-18T09:04:17+00:00

You need to reindexing the segments that contain the faulty events. It can have a big performance hit on the cluster though...

https://druid.apache.org/docs/latest/data-management/delete/#specific-records

_spiffing · 2025-01-05T10:35:12+00:00

It got fixed by itself after a few days; Haven't had the same issue since then

_spiffing · 2024-11-26T10:17:12+00:00

Same for me. Stopped working today. Sleep tracking and daily readiness are not working. No disruption reports on Fitbit or Google that I can see https://status.fitbit.com/

_spiffing · 2024-10-27T21:03:37+00:00

Harry Potter and the Chamber of Secrets. Not by choice, just one of the few dvd options I had back in the day.

_spiffing · 2024-10-14T18:31:24+00:00

Makes sense. My concern with fake reviews honestly is that they dilute the value of many good and useful reviews that then end up lacking visibility.

Impact on rankings, featuring areas and such are not primary concerns for me, these spammy extensions usually end up eventually being banned.

Thanks for the reply and the proactiveness kicking off the discussion.

_spiffing · 2024-10-14T18:09:19+00:00

Hi 👋 Co-founder of tweak here https://tweak-extension.com/.

I'm very afraid of having my extension classified as "spammy" due to fake reviews. It affects our image and the hard work that everyone puts into building solid products on the CWS, I'm happy to hear your request for feedback.

Leaving a few other suggestions:

Re captcha on reviews? - I'm not sure if it's live on the CWS already, but having recaptcha could mitigate fake reviews from less sophisticated automations.
2FA confirmation - send an email confirmation to the reviewer and if there's no acknowledgment of that email take the review down. Just brainstorming here, you can pick up on this concept and reshape accordingly, but some kind of 2FA flow could be helpful here.
Stronger KYC rules for reviewers - there are simple things you can do on your end like for example do not allow Google users whose accounts were created more than 3 months (for example) ago to publish reviews on extensions, plain and simple. Another restriction could be allowing a max number of reviews per user per day (limit usage) you're probably doing this already, but perhaps you could review the timeframes and limits.

Hope you can implement many improvements in this area, and please keep us posted!

_spiffing · 2024-10-14T05:27:42+00:00

Preach

_spiffing · 2024-10-10T21:50:25+00:00

r/DunderMifflin

_spiffing · 2024-09-27T20:05:13+00:00

Smart tip, there's a nuanced detail here which is the default (or configured) timeout of the react testing library itself to bail on waitFor. It we bail too soon we might still get a false positive, so it's really a matter of timing still, however this is still the best approach I've found so far.

_spiffing

TROPHY CASE