Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
hacketyhack
the coder’s starter kit: sound, animation, video, messaging in a low-key ruby environment.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
Quil[0] repo has either a homage to _why, or _why has contributed the intro.
[0]: https://github.com/quil/quil
I like to start with live coding exercises, think Exercism[0] or Codewars[1], to get a good sense of the syntax and basic appliances and then do an actual project with real documentation on the side.
Tutorials just don't cut it for me, they never have. It's just a grueling format and it does nothing but put me off the tech I'm looking at.
[0]: https://exercism.org
[1]: https://www.codewars.com
My first post was poorly written. I didn't mean to imply that taking pride in a job well done was bad. I don't think it is. I think programmers have plenty of reason to be happy when they do good work[1]--what I think is foolish is having visions of grandeur when it comes to programming, which in my opinion is what _why seemed to have based on his reasoning for quitting. I could be way off mark, but that's my take.
I mentioned this in another comment, but I think it also has to do with a confusion of categories. _why seemed to want recognition akin to that received by, e.g. Thomas Bernhard, Kafka, for something like shoes or his other software/libraries or general contributions to computing. But the issue is these things will always be utilities for specialists, and any aesthetic properties they have (elegant design, expression, etc.) are secondary to their functioning and they'll always be relegated to the dusty realm of specialists since the code is not the product--the software is. One can write code to create an aesthetic object that is enjoyed and revered by the masses, but I have a hard time envisioning a future in which the masses will ever enjoy and revere code or engineering for its own sake.
Pride was the wrong word to use and one I lazily reached for. After reading your comment, you've helped me realize that what I advise against is misapplication of expectations to different categories of things. _why seemed to want an aesthetic reception and legacy on a general, popular scale for work that is ultimately only a utility to the vast majority of the population and indeed, not even accessible to the population, and even if it were, I don't think many people would admire programming libs for fun--such a hobby will remain the lot of only enthusiasts. There is no pop coding like there is pop music.
[1]: Though I'd also argue that much of what you state taking pride in is not programming--which is just expressing ideas in programming languages--what you are talking about is engineering/design, which can be done perfectly well and separately from the programming part. we just happen to solve a lot of problems with computers these days so we need to express solutions for computers to consume and we tend to blend those responsibilities (we'll one day get to a point where the computers do most of the programming and we just design https://github.com/nadia-polikarpova/synquid)
I like to think he addressed this when he reappeared a few years later:
"Now I want to make it perfectly clear that these papers and all my other works in life belong to the general public. In fact, I also would like to turn myself over to all of you as well. This was actually done several years ago, but in an embarrassingly disorganized manner." - https://github.com/steveklabnik/CLOSURE/blob/master/PDF/DISC...