I genuinely feel that companies with existing well designed systems with intentional architecture and design patterns will have far more leverage, with AI coming into the picture - as opposed to upcoming systems which are vibe coded from day 1.
Try PianoForAll.
My experience, fwiw - Pianoforall was instrumental in helping me play real music at parties and make the piano journey rewarding and enjoyable early on. Without that, the early days of learning classical music, music theory, practicing scales, ballads etc were a limbo - you don't feel like you are making progress (even when you are).
That said, PFA only compliments your classical syllabus, not replaces it.
Here's mine:
0. Build the habit of taking notes ruthlessly to build a comprehensive second brain.
1. I transitioned to the penhold grip in Table Tennis in Nov 2025 and it has been a fun exploration. My goal for 2026 is to learn to play all the strokes comfortably with the penhold grip, and start competing at the district level.
2. Go from novice-intermediate to upper-intermediate in piano playing. Learn, memorize, and perform flawlessly 30 advanced piano pieces (minimum Henle 7–9) end-to-end, recorded on video, within the next 12 months.
3. Learn to speak Kannada. Been living in Bangalore past 9 years and it's almost embarrassing to not know a single complete Kannada sentence.
Just curious, does it matter? For some simple boilerplate code, simple test cases and simple skaffolding, which is needed in most applications, do you even care?
I'm yet to find a convincing definition for super intelligence. "Intelligence that surpasses human brain" is such a half hearted definition that I don't know what to make of it.
It would have made sense to have GraphQL support in cURL, had GraphQL been a standard transfer protocol rather than a query language. Support for query languages is out of cURL's scope AFAIK.
This is where GraphQL shines. You give your developer a schema and "they" choose the queries and mutations they want to make to make their life easy. Also, there's very less friction because the GraphQL schema can be completely documented.
And while going to prod, you just allow the queries that are being used, disable rest.
You can avoid this by allowing only specific queries in staging and production environments, this way, the introspection query can be disabled too.
Not sure if this violates the GraphQL spec though, because, ideally the server supports introspection, but it is disabled in some cases for safety reasons.
1. Have you tried mindfulness meditation?
2. Which type of mindfulness meditation have you tried?
3. Why do you think it is useless when most people find it useful?
4. With what goal did you try the meditation that it seemed useless?
You cannot throw a word "useless" without emphasising the "use".
> Not everyone is perfect just how they are but everyone doesn't have to act the same way to be acceptable.
This undermines the very concept of "law and order". There "must" be restrictions on behaviour if it is intrusive, offensive, inflamatory, indecent etc. I think it is okay to have an enforced "code of conduct" to prevent assholery.
I respectfully disagree. I think most people would be okay with "average aesthetics" as long as the functionality of the product is designed well (flexible batteries in this case)
What looks good to 5/10 people, might not look good to the other 5/10. For an instance, consider an iPhone 4S. It is a pretty average design "aesthetically" IMO. But the phone did extraordinarily well because it was a well engineered phone. Another example is this website that you're looking at. I would call this average aesthetics as well.
Of course good aesthetics is an awesome add-on, but it is not fair to disqualify a product based on just aesthetics.
I slightly disagree because I prefer the code to be consistent all across my codebase.
Sure it is some effort to backtrack to the util functions, but I think the effort is worth it because I would rather have a developer spend multiple hours debugging and figuring out the code than having something that is a nightmare to iterate upon.
Disclaimer - Author