westoque

> It absolutely is a harmless feature that you can ignore. There’s no reason not to have one

what i've learning developing and creating products over the years is that harmless features tend to be the ones that cause the most problems. for ex, now you have to add touchscreen code to the OS vs previously not having it at all. and this code or feature we will support for the rest of the lifetime of that product.

funny anecdote. i was traveling in europe around 2011 and i was staying at a hostel. the hostel had a session where all the travelers go in a circle and introduce themselves. i mentioned i was from "america" and this south american lady got triggered and said "you know there's also SOUTH america right?" and after that i never used the word america anymore and just say i'm from the USA.

not a fan of README's where there's no clear way to run the program, like a getting started or how to build. i think this is the opposite of a docu-monster where AI documents everything, but clearly more documentation is better than lack of.

> But like every habit, the only thing you have to do is to keep at it. And if you pay enough attention to it, something will click in your brain.

a bad habit i noticed after taking hiatus of focused work was me jumping into different windows and tabs and just mindlessly consuming content without finishing them. after noticing this pattern, i decided i will focus on one task at a time and finishing it, like reading the OPs article. it did wonders for me and i noticed i'm now even more focused that ever. the lesson is indeed being aware first, and then practicing the habit.

ok. a similar idea, you should put a camera outside your door and do the same for passing dogs.

my idea of de-brainrot is by going to destinations where everything is new and experiencing everything there physically & mentally. either going to a new city or drive to a new place. i'm not sure if it's anecdotal but there's a feeling of astonishment when experiencing a new place. i find that when you go back you have this new perspective and you feel refreshed.

with agent loops, the cost of exposing bugs should be cheap now. every pen tester should be using agent loops and on the flip side, an agent could easily see this issue once filed and a fix immediately done. it's incredible how cheap code is now.

this is exactly my setup! the ipad pro 11 m5 cellular is such an amazing device especially with the 5G. only downside is obv the iPadOS, it's still very limiting and shortcuts and power tools (like easily prefilling passwords) are non-existent. for passwords, you still have to manually click the pre-fill and/or enable full keyboard to be able to tab into it but still annoying.

i can see the resemblence and that's what separates the more marketable app.

i just did an AI hackathon and 90% of the submissions were written in TypeScript and Next.js which is mostly due to the training data. AI is skewed to use these tools by default vs the best for the job.

I don't think random blogs should be ruled out. Just because a blog is random doesn't mean its untrue.

> Comparing agentic Qwen3.6 35b to Claude Opus is like a junior with knowledge across the board, that you really need to guide, versus a senior that thinks with you on architecture.

that's why i use the frontier models because its a senior co-worker vs a junior. if you use the junior for the sake of privacy i think you're missing out on the best insights for a specific task.