'Our first encouter with AI in the form of LLMs, within the product of ChatGPT was very much like an oracle. You ask a question, the oracle speaks, and that is the transaction. '
Chatgpt moment just like google back in the early days truly felt asking an oracle a question.
Unless you made the mistake of having your question be something you knew about, in which case you would be forever cursed to see the janky contraption tucked behind the curtain.
Mine also got flagged the moment I posted it. First I was shadowbanned, managed to somehow get unbanned then can't even post my show. But here is the reply I got, and it seem to make sense:
''On HN, the idea is for people to submit stories that they ran across and personally found intellectually interesting, not because they have something to promote. It's fine to post your own work, as long as it's interspersed with interesting posts from unrelated sources. But when an account submits promotionally, it feels like they're not participating as a community member, and HN users notice this and flag the posts.
It's best to build up a track record of interesting submissions from unrelated sources, and to intersperse your own articles with those. The software considers submission histories adaptively, so if you do that, your own-posts will eventually stop getting filtered.
If you dig up interesting things from a variety of places, things people haven't run into before, then you'll be perceived as a community contributor rather than someone trying to market something. Particularly good are stories on out-of-the-way topics that rarely or never get attention. The best submissions are the ones that can't be predicted from any existing sequence.
(Note: avoid posting major sites like youtube, twitter, medium, etc., for this purpose, because the software classifies them alongside the promotional posts so they won't help 'dig you out'. Ditto for Show HNs and Ask HNs (text posts) - avoid those until you're in the clear.)''
calling AI a hype like it is a vaporware makes me want to read that even less. AI has made a lot of difference last 3 years and will probably do 10x more in the next 4.
But why do agents need a skill to find skills? The security nightmare aside, don't they already have access or the ability to dig into what they need to do
For the security nightmare I have taken precautions, and by default only skills from trusted repos are given.
They could potentially websearch and find new skills, but that is tough, and of course will not be able to reach niche skills, that would be perfect for your use case. I have created semantic search with a ranking algorithm to give the appropriate skill in an instant.
Oh man, lots of dead ideas. Atm attention is more important than ever, cos delivering on ideas got easier. Getting the attention your product needs got harder
Did delivering quality really get easier? I'm certainly not seeing it in the software I use. Delivering scale doesn't mean the mission was executed well.
Judging from everyone I know, it will take people a lot of time to learn and accept a lesson from decades ago(one from before some of us were even born and I'm in my mid 30's): lines of code is a shit metric. Sloppers tend to believe that something seemingly working = production ready = good execution. And the metric, of course, is lines of code or "tokens". Until then, the list on this website will keep growing exponentially.
> I always suspect there's redundant nonsense in any code module I haven't myself inspected.
I don't think this is arrogance in the sense that it's probably correct. It is however pretty easy to take that line of thinking into an arrogant attitude though, which is the real issue.
Seniors are no different and that infuriates me even more. The few times I felt lazy and let an AI do a simple function for me, all hell broke loose. I'm starting to think that many people were never that senior to begin with: Writing the code accounts for very little of what development requires and is often the easy part. Understanding the problem and finding the sweet spot/optimal compromise, edge cases and how you can break it is what has always been difficult. Seeing github explode with slop and github(microsoft/openai) themselves push even harder should be a wake up call for anyone that understands what development is: not writing the code but having someone else go through it, analyze it, understand the problem you are trying to solve and why you made the decisions that you made - that pretty much always takes a lot more time than writing the actual code. And then I see someone push 20 commits in a day, each being 5000 lines, jam packed with emojis and other slop and tell me that they carefully reviewed all of them? Yeah, that's bullshit, mate.
I once worked at a fairly large corp that considered itself tech-forward (it was a retail ecommerce company), and at one point they just decided to demote all engineers one level because they somehow finally realized that everyone they had been calling "Senior" were definitely not at that level.
Just like how more RAM and compute in the cloud made us worse engineers (no need to turn your brain on to tune performance).
When the brain is off for one thing, it's off for the rest as well. There is a lot of talk about "we don't have to think about code so we can think of ideas", but that's not how it works. We just don't think.
They should put microphones in the cloud servers so you can hear the fans spin up when you run a program. It's a bit more impactful than a silent CPU usage graph.
Chatgpt moment just like google back in the early days truly felt asking an oracle a question.