Lisp:
(
a
b
c
)2,383 karma · joined February 4, 2021
(
a
b
c
)The easter egg looks quite cool :)
https://www.fuckupmysite.com/?url=https%3A%2F%2Fwww.fuckupmy...
Don't know whether this is failure or resilience.
So people started slacking off, because "you have to love your employees"?
Since the last Emacs dropped, in fact, which I'm sure is unrelated.
The download mirror is still accessible: https://ftpmirror.gnu.org/
Being highly programmable is part of our distinction. You can't build any of these things, but you can learn to build all of them.
Your possible pinnacle isn't just not chewing the couch.
Can't wait for Lisp to be the language of the future again.
Some of my friends reckon it'll happen the year after the year of Linux on the desktop. They're on Windows 11, though, so I don't know how to read that.
I don't think this holds.
JavaScript was created as a frontend language specifically for web browsers.
It wasn't until 2009 with the introduction of Node.js that JavaScript became a viable option for backend development.
The web was already the dominant platform by then.
Is that a consequence of the majority of available training data, or are they all massaged that way?
The uniformity of political leanings contrasted to the variability of IQ seems to indicate massage rather than training data, but I can't be sure.
I get them at my local stationery shop for €0.80, but theirs don't have brass discs.
Then write for forums. Let me briefly elaborate.
In a forum, the conversation is already going,and you catch it at a place that interests you, and throw in your two cents.
In a blog, there's too much ceremony: find "blog worthy" idea, do "blog worthy" research, write "blog worthy" prose, review and edit "blog worthily", publish.
Too many hassles, and perhaps some psychological barriers here or there too.
When you have an intetesting thought, use the forum as the audience in your mind, and write your response to your thought. Take this or that position, turn them on their heads, contrast and combine them, play around with them.
Then save and close the file, and let it steep. Come back to it when you remember it, or when it starts bugging you, and when you feel ready make a paper plane out of it and chuck it out the window to the winds, i.e. turn it into HTML and put it somewhere online. Ask some friends for feedback and their thoughts, retouch your thinking and your text. Lather, rinse, repeat.
You will consistently have ideas and counters ideas, it's unavoidable. After you have a rudimentary technique down (and forums grade/conversational is perfectly adequate) the rest is just imprinting your thought process on paper/into a file. It doesn't need to be written for fanciful reasons, thinking through writing is perfectly legit.
Then one file will lead to another, and then another, when you feel like it, because your writing muscle will strengthen. You don't need a daily/weekly/monthly schedule, unless you want to adopt one on purpose.
You can also read around the tech blogosphere for more inspiration, posts on writing or blogging is a frequent blogging subject :)
Given how we're on HN, I'd be amiss not to recommend a read through PG's essays on writing, and I also find Dan Luu's also interesting (https://danluu.com/writing-non-advice/).
Reading these, don't take them as gospel but as tasters, gauging your feelings about this or that approach, and fleshing out a process that works for you, understanding your likes and dislikes. Then accept your process.
But don't start with writing a blogging engine, for God's sake :)
It's right there, linked to from TFA's first paragraph:
That's a soon to be ex employee.
Personal anecdata from a software team in a non-software company:
New project idea comes in. Developer asks for outline of specifications. Management replies with nebulous desires.
Developer insists over half a dozen "planning" meetings, where desires are mentioned but requirements not defined, despite all petitions and cajoling. Management fires developer for not being a team player.
From what I hear, that project has yet to happen a year after the aforementioned events.
And that's without criticizing, only with explaining the value of specifications before developing business critical applications.
So, yeah, employers get what they pay for: either sheep or conscientious employees, but can't have both.
What still isn't there is the concept of image-based development, but this seems to be intentional, while environments and containers tend to replicate some of that functionality.
Though I think Lisp's approach still remains a unique way towards "programming as theory development", or "programming as teaching (the computer)" because of the particular power of its treatment of the REPL as a long-running, uninterrupted environment.
Seems to me that the focus should be on institutions as power centers, rather than beliefs or loosely defined "religious people".
Illich himself also noted how institutionalization of an initially revolutionary idea reverses its meaning, switching, say, liberation into oppression.
Power grabbers will always attempt power grabs, and will eventually distort an initial good idea. They will pretend to Embrace it, then attempt to Extend it with their own input, to finally Extinguish the original idea.
My Shift key seems to be Jittery, apologies :)
Granted, an autodidact programmer might have encountered the concepts, but a CS graduate must have.
In my case, I was an autodidact well before I went in for Electronics Engineering. Because of personal interest, I put in a lot of time into these things, and did get to know them, but didn't really hear once about them in EE.
I guess if one engages long and deeply enough, they'll get to a high enough level - they'll acquire "sufficient expertise", per PG's turn of phrase. Conversely, no amount of CS courses will get one any wiser if they don't pay attention.
Everything always depends.
For personal projects, though, I get the value of an actual small projects monorepo.
I think I read the same text in a 1996 reprint some years later, in 1999 - coincidentally also during my last year of highschool with impending doom^Wexams afoot.
Definitely mind-expanding, and helped shape my early cyberpunk tastes, though it didn't get me hitched :)
I do think the translation was excellent, he definitely must have put hard work and passion into it!
From TFA (emphases mine):
> This guide presents our evidence-based recommendations for maximizing your impact over a 1000-year career.
It's more like playing dumb, willfully ignoring the issues to serve ulterior motives.
Connection managers started dropping about one hour ago, and up to a few minutes ago there were one or two thousand people in-game. Now it's dropped to absolute 0, eerie :)
W.r.t. natural languages, TFA clarifies it a bit:
> And it’s not the same as translation to Arabic or Hebrew; direction here refers to the temporal order in which the tokens are produced; even for right-to-left languages, the order in which the tokens get produced remains unchanged; rather, a thin display layer handles the visual presentation.