why physical books are better than ebooks
Readers are faced with one of the most complex decisions: to read a physical book or to read an ebook. Now, both probably have their pros and cons. But, I am here to tell you physical books are far superior to ebooks and as someone who owns over 3 books and a Kindle, I know I am a trustworthy source.
To put it simply, you can do a whole lot with books that you simply cannot with ebooks.
Books can be touched and felt. Books can be sniffed. Books can be annotated with a pen. Books can be copied and distributed illegally or used for training AI models. Books can be torn. Books can be burnt for warmth. Books can be eaten, with a surprisingly low chance of indigestion. Books can be dipped in chai until the sturdy pages absorb enough to become flimsy and even dissolve in the chai.
Books can be thrown at people without hurting them as they spread out like a parachute before it reaches them. Books can be fried in batter and fed to children. Books can be buried without sullying the environment.
Books can be abandoned in houses and eventually fed to mice. Books can be judged by their cover. Books can be arranged out on a bookshelf to signal your intellectualism or unveil your i. Books can be repurposed to hide weapons, gold, or contraband.
Books can also be read, but I put this last, because it's not much of a strong point against ebooks, but just noting it can also do the one thing you can do with ebooks.
Don't be a sucker. Buy real books.
https://atharvaraykar.com/books/
#physicalbooks #ebooks #kindle
#rss #feeds #linksharing #qwibbit
#physicalbooks
#ebooks
#kindle
#rss
#feeds
Atharva Raykar (Unofficial)1h
disgraceful in aggregate
The whole is never just a sum of the parts. There are lots of things that I find to be disgraceful only when taken in aggregate. But any individual instance of it seems okay, and so I look odd when I object to any of these things.
Mobile notification sounds
Modern car aesthetics
Most boxy streetwear
Technology meetups
That Pop Psychology Writing Voice
Apartments in Bangalore
This is the classic problem where every party involved is mostly making reasonable decisions for themselves, but it really lowers the tide for everyone as a whole.
These are problems that don't bother me too much, so I don't do much about them. However, if I were to go about fixing them, perhaps the solution is displacement rather than boycott.
https://atharvaraykar.com/disgrace/
#aggregate #disgraceful #poppsychology #psychologywriting #voiceapartments #however #mobile
#rss #feeds #linksharing #qwibbit
some of my unpopular beliefs
I hold many beliefs that are unpopular. These are some of them. I will not share all of my unpopular beliefs, because it is unwise to do so publicly. My selection criteria is that these are unpopular but still within the threshold where someone might inquire them and come to see things the way I do, or pitch a solid case to me that might convince me to change them. I also do not include beliefs that are not actually unpopular but are treated as such depending on which bubble you ask (eg: "capitalism is fine" or "religion can be useful").
Being the 90th percentile best at something is not that hard, and most people can be 90th percentile at pretty much anything. It just so happens that just about no one tries. So it follows from this that:
Most people are generally operating at 10-20% of their full potential.
Being 90th percentile good at one thing is not super impressive.
Because most people are operating at 10-20% of their full potential, being born especially "gifted" at something isn't that useful in practice, it can be easily overcome by those who bothered trying. For example, these blind archers will shoot better than me any day of the week.
Happiness is a manageable problem for 90% of the population (perhaps 99.9% if you are privileged). It's not possible for everyone to evade sorrow and be happy at all times but you don't have to try and control this. You just have to learn to be okay with life as it is. Nearly every culture has fairly practical ancient philosophy that tackles this issue head-on and presents mostly correct solutions that work for most people, but as mentioned above, pretty much no one actually really properly tries them out.
Related: It is easier than ever to tackle the problem of sorrow and dissatisfaction in 2026 than in any other time in history.
If you want to change how the world works, you are also obligated to accumulate and wield power to make that change happen. It is not right to want a change without wanting to be a change agent who is willing to also be held accountable for a change.
Everyone is deserving of empathy and consideration, including bad/evil people. This is not the same as being tolerant of bad/evil things. It is rather that they must be understood and deserve the same curiosity as everything else.
The only true "safe space" can be created in the mind (however, this does not mean you are not obliged to protect the safety of the marginalised).
It is incorrect to be more concerned about global far-off goings-on than it is to be concerned about things closer to home (or literally at home).
It is generally good to fail hard and often in life, as long as the failures are reasonably recoverable.
We are all way too judgemental. This is a huge character flaw in pretty much everyone, and one of the hardest to fix. I can't think of anyone who was obviously completely non-judgemental (judgement is not the same as discernment, the former carries a negative aura).
https://atharvaraykar.com/unpopular-beliefs/
#unpopularbeliefs #everyone #because
#rss #feeds #linksharing #qwibbit
#unpopularbeliefs
#everyone
#because
#rss
#feeds
Atharva Raykar (Unofficial)10d
Programming
0:00 / 0:00
a song I keep coming back to
&playing&window.YT.Player
It first occurred to me when I tried out Windsurf. This was the old Claude Sonnet 3.5. The AI made a few edits to my code in response to my query, in quick succession. The code was bad, and it didn't work. However, this was enough. I always thought this might happen, and when it finally did, I felt mentally prepared for it.
I knew this was the beginning of the end of my software engineering career.
It had just been about two and a half years since writing software professionally, but really, I had been programming for quite a lot longer than that.
A decade and a half ago, I was already really into technology. The first program I ever shipped was in VB.NET, after looking up a YouTube video to learn about programming. Why did eleven year old me pick up Visual Basic of all languages? Well, I didn't want to do C++, I knew that would be coming up in our high school curriculum anyway. My brother was already learning Java, and I didn't want to learn whatever he was learning. And Visual Basic seemed to have a nice IDE with drag-and-drop GUI assembly. I built a GUI calculator app, and then excitedly recorded a demo of me showing it off, my prepubescent voice grandly reading out the values as it added, divided and multiplied two numbers. It eventually threw an ugly default popup when the types didn't match because I did not bother handling the exceptions.
A still from the demo of my first program. Yes, the desktop gets better the longer you look.
After this, I was doing a lot more programming in my free time. It was satisfying to learn the incantations that made the computer do things for me. My favourite class in high school was the computer lab, where I, being the precocious programmer whiz would whizz through all the assignments, so that I could start messing around with programs I actually wanted to write. It was around this time, I aspired to be an open source contributor, rather than just a consumer. I discovered...
...Wait. I know what plenty of you are thinking. You've heard this story beat before. He's going to pick up Python, Javascript, C++, read all sorts of books and tutorials, and slowly unearth the history of this field and its pioneers. Dijkstra. McCarthy. Thompson. Kay. Torvalds. Yada Yada. Oh well, looks like he bumped into Lisp. He read Paul Graham. He chose Racket after seeing Butterick's beautiful website on typography and seeing how it was written. Blah Blah. Now he's also a functional programmer. Yakety-yak. He's reading through Alexis King's Parse, Don't Validate and then Bob Nystrom's What color is your function? and then going further into rabbit holes of program design, abstractions, control structures, and whatnot. You know the drill. He watches Strange Loop talks instead of Netflix like any other normal person. He's not going to just be any programmer, he's going to be an elegant programming craftsman. And with such cool programming taste.
He's then going to start an Open Source club in his college. He will get on a student program to work on Git through their mailing list (unlike the heathens using GitHub), getting his patches personally pulled apart by the fantastic Junio Hamano, the lead maintainer. He's going to make friends with people who help pique his interest in distributed systems and databases. He's going to join a group of brilliant Clojurists who then really help him sharpen his axe, and induct him into the brilliance of Rich Hickey's philosophy. He gets blown away by these "greybeards" and thinks of becoming one of them someday. He had so much to learn, and he was on the come-up. Still green, still full of potential.
And then you know how the rest of this beat goes from here. This AI bulldozer comes through, and the rest of the article is going to be this guy pouring out his feelings and processing his grief for how the profession has changed. The craft isn't what it used to be, and the magic, the joy is gone. The skills I have spent years developing all turning into mist, all getting displaced rapidly.
And this is where I stop you and say, hold on right there.
I actually don't care.
All accounts would say I should be the guy that feels something about what AI has "snatched away." Didn't he wax poetic about the brilliance of Clojure not long ago? Now, hardly before he could really climb through the ranks to become a true master craftsman, the whole way of programming was upended right in front of him. The AI (at its best) can write more sophisticated code than him at an unfathomably quick pace. The roles and the career paths that were available to him no longer exist. Yet, I was unbothered.
If not grief, maybe my response could be embracing the changed craft with a certain youthful degeneracy of a Steve Yegge perhaps? Nope, not even that. In fact, by the time I realised it was the beginning of the end, I was already quite casually thinking of all the ways in which I would choose to not be the great programmer craftsman. I, of course, still value the craft, but I don't feel like I'm some God's chosen vehicle for it. All that matters is that my initiatives are able to produce something useful and usefully tasteful for the world.
You see, I thought I was that kind of guy, this boy programmer to craftsman archetype, but it turns out I wasn't really. It was true that I enjoyed all of the things the community I surrounded myself with enjoyed. But sometimes it felt subtly offâlike I didn't quite belongâor the way I enjoyed it wasn't quite like how people I looked up to enjoyed it, in rather inarticulable ways. To perhaps use a macabre analogy, it was like a case of a "great imitator" autoimmune disease where I was misdiagnosed.
I don't quite know what the real diagnosis is. I have not yet found the thing to be long-term obsessed about which people say is a prerequisite for doing truly great things. But the pattern I have seen is that moreso than programming, I am really drawn to ill-structured domains of work. A lot of software engineering work is that way, though not all of it. A big chunk of the programming community is about interest and obsessions with programming structures and concepts, something that felt rather pointlessly recursive. Time and time again, I'd go to conferences and work environments where status is conferred based on how virtuosic someone is at programming. This was initially fun, but over time, I felt more and more estranged from this culture. For me the arena was out there in the world around me, and not in the screen. The brilliance and wonder of technology loses its way before it can make it to the average human, and as a result, most technology sucks, and I kind of hate having to touch and use most of the technology available to me.
So where does that leave me? I don't think I'll ever stop writing programs. Quite predictably, I ended up being a rather early adopter of the new way of agentic programming. But it wasn't what ultimately drove me away. Programming won't be my identity, because the world is much bigger than that. Perhaps identifying with a single profession in today's world is simply not my jam. The world is too deeply interconnected for that to be helpful.
https://atharvaraykar.com/programming/
https://atharvaraykar.com/media/108
#programming #visualbasic #claudesonnet #gui #windsurf #yada #blah
#rss #feeds #linksharing #qwibbit
a few "late" bloomers
There's a huge bias towards talking about people who were very notable or "successful" when young. So here are some interesting people who came through a little late.
Kevin Kelly
I always admired Kevin Kelly's approach to work (than his actual work, which, while interesting, I haven't engaged enough with). His real notable breakthrough happened only when he was 31 when he was hired by Stewart Brand.
Robert Moses
Not everyone in this list is going to be a good guy. Robert Moses, by all accounts was a terrible person, but I was surprised to learn that before he became a broker of power and terraformed New York, he was just a complete and total failure. He practically wasted away his 20s in the Bureau of Municipal Research, and what he had to show was a failed policy proposal, and a dead-end career, where he struggled with even finding a job. It was a phone call from an old connection that gave him a second wind.
Robert Caro
Not only was Moses kind of a late bloomer, so was his legendary biographer, Robert Caro, and perhaps the greatest investigative writer ever. Yet, he was pretty much a nobody (though obviously a rather competent nobody), and in his words, "plain broke" right until when he published The Power Broker, at the ripe old age of 38.
Shawn Wang, aka 'swyx'
Everybody in the AI engineering world has heard of him at this point. Though I used to enjoy and occasionally read his blogs before his AI era during COVID. I was surprised to learn that before that, he was pretty much an unknown guy. He had a well-paying finance job that he burnt himself out on, and at the age of 30, taught himself to code via freeCodeCamp. He seemed to have a hit a hot streak, that's been going on since. I had the opportunity to meet him in person during AIE World's Fair, and as the most busiest (and likely enormously tired) guy leading the show, he was still super kind and considerate!
James Murphy
LCD Soundsystem is one of my favourite bands. I really enjoyed seeing this interview of his where he said that he was basically a complete failure, playing in bands that went nowhere, and completely coasting in life. Then after some therapy, he realised that he was just not taking any risks, because he was afraid of failure, and wanted to keep up his image of being this smart guy that everyone was telling him he was. His first hit single, Losing My Edge, came out when he was 32.
Rich Hickey
I still consider Rich Hickey's greatest contribution to not really be Clojure, but rather the clear thinking and the philosophy of how to solve problems that came with the talks accompanying it. Turns out, Clojure and all these talks came out of his retirement savings. He was well past his 30s when he became known.
There's a lot of good to be done in the world in many capacities at any age or time, and it's a bit of an ego thing for a person to pay attention to their age for "success." These are all made-up boundaries, everyone dies at the end anyway, so it just makes a lot more sense focus outwardly on the world rather than inwardly about your narrative.
https://atharvaraykar.com/late-bloomers/
#robertmoses #kevinkelly #robertcaro #late #richhickey #stewartbrand #world #newyork #clojure
#rss #feeds #linksharing #qwibbit
Welcome to Atharva Raykar (Unofficial) spacestr profile!
About Me
Unofficial automated RSS/Atom links from the source Atharva Raykar, covering Observed relevant material in sampled entries (art, math, translation, software, book). Original creators are credited at the source; follow original links. Zaps support the independent feed operator, not the source creators.