It’s both functional and a great party trick.
4,146 karma · joined November 14, 2013
LinkedIn: https://www.linkedin.com/in/tyleo/
It’s both functional and a great party trick.
https://www.tyleo.com/blog/the-terminal-star
A lot of good comes out but it can be hard to separate from the parts that just take advantage of your brain.
Most games are expensive to make and most of them fail. Way more than normal software which doesn't have ultra-high marketing costs or diverse staffing needs (Art, QA, game design, etc).
Like all team building I feel like the fundamental question is, “what works for this group of people?”
Rather than “teams with/without calls is superior,” and slamming every team you work with into it.
We should only need to specify observable behavior... but observable behavior is so broad that it includes common defects... but also we shouldn't need to specify the lack of defects even though they are observable.
It feels like, "the AI should read my mind and do the right thing without me fully specifying it."
Memory leaks, deleting the hard drive, spending money would all be observable behavior.
By your reasoning that the "observable behavior needs to be specified rigorously" it seems like you'd have to list these all out. We do, after all, already have cases of AI deleting data.
That sounds harder and more error prone than what we're doing now by rigorously defining these defects out of existence in code.
Those idle screens taunt me with a desire to use them for Slack or Hacker News when I’m trying to work.
When you don't know the answer to something you should try to figure it out before asking. That builds important skills. Like it or not LLMs are now a useful tool for that. The first instinct shouldn't be to ask someone else if you haven't expended any effort.
For example, if you don't know 6*27 I'd consider it rude to ask if you have a calculator on your desk but you're too lazy to use it.
I think it's an open question of whether we achieve the holy grail language as the submission describes. My guess is that we inch towards the submission's direction, even if we never achieve it. It won't surprise me if new languages take LLMs into account just like some languages now take the IDE experience into account.
So something which must be true if this author is right is that whatever the new language is—the thing people are typing into markdown—must be able to express the same rigor in less words than existing source code.
Otherwise the result is just legacy coding in a new programming language.
It's interesting that this is so polarizing.
1. Asking a question which could be answered by an AI
2. Pasting an AI response to something
If 1 is fair game, I'd say 2 is too.
Speed without judgement always compounds badly.
If we moved to a wealth tax I'd be the first in line to pay it. So long as everyone else had to pay it too.
Hell, I'll be the first in line to pay the damn tax so long as billionaires are right in line with me too.
A lot of blogging is reputation and consistency. The other part is audience. It looks like he's been at this for 3 years. There might just not be an audience for it. If that's the case, and the hustle doesn't bring you inherent joy, it probably isn't worth doing.
* Note that it may be misattributed to him
In my case I just use AI to fix typos and save people time if I repeated myself in a message.
You’re foaming at the mouth a bit about AI here rather than reading what I said. I don’t see how shortened or fixed grammar is slop. The article argues the opposite.
I’d love to see you rise to the challenge. If you think there’s an opportunity to make money here, “lots of ways to make this work,” perhaps take it up yourself.
Is the world really better if those people face additional burden? Does it create a fairer system that helps indies succeed? Does it encourage creativity?
And the Hacker News title should be changed to the slop title in the article, "It's Not The Terminator. It's worse"