This is not to deride feats of AI today, and I am sure it will transform the world. But until it can show signs of human ingenuity in making unexpected and far-off connections like these, I won't be convinced we are nearing AGI.
10,569 karma · joined December 28, 2012
Currently working on: https://textquery.app/
-------------------------------------------
Blog: https://shubhamjain.co
Email: hi [at] shubhamjain.co
Twitter: @shubhamjainco
This is not to deride feats of AI today, and I am sure it will transform the world. But until it can show signs of human ingenuity in making unexpected and far-off connections like these, I won't be convinced we are nearing AGI.
I know, I know, this could just as easily be a double-edged sword. A database should prioritize stability above everything else, but there is no reason why we shouldn't expect them to reach there.
a) That a palm-size laser projector could work as a display.
b) That awkward hand gestures are a great way to navigate UI
c) That voice could work as a primary input.
d) That people would be willing to pay $700 and a monthly subscription for a device that barely works.
It's at par or even worse than Juicero. The team and its supporters should stop hiding behind "it's v1", and "we were trying to invent a new paradigm." The device has to be promising now, not in some imaginary future. And trying to invent shouldn't mean you're going to forgo questioning the basic foundational ideas.
I am kind of surprised that the idea was Paul Graham's. I always assumed that it was Steve and Alex who came up with it. Considering HN was also started by PG, which has survived and grown with just a few changes every year, I think he has a unique talent for creating lasting online communities. It's not an easy task, btw.
> I think goto's are fine, and they are often more readable than large amounts of indentation. That's _especially_ true if the code flow isn't actually naturally indented (in this case it is, so I don't think using goto is in any way _clearer_ than not, but in general goto's can be quite good for readability).
[1]: https://koblents.com/Ches/Links/Month-Mar-2013/20-Using-Goto...
An important reason—amongst others—why projects like ChatGPT cannot be conceived inside Google anymore. Yeah, it's sad how legal, privacy, and compliance teams have expanded to obstruct any significant engineering project, but there are genuine reasons why.
Larry Page's original ambition was to digitize books and knowledge in the world [2].
> Page had always wanted to digitize books. Way back in 1996, the student project that eventually became Google—a “crawler” that would ingest documents and rank them for relevance against a user’s query—was actually conceived as part of an effort “to develop the enabling technologies for a single, integrated and universal digital library.”
[1]: https://twitter.com/jam3scampbell/status/1608270969763729415
[2]: https://www.theatlantic.com/technology/archive/2017/04/the-t...
> It’s tempting to think ‘So what?’ and dismiss these details as incidental or specific to stair carpentry. And they are specific to stair carpentry; that’s what makes them details. But the existence of a surprising number of meaningful details is not specific to stairs. Surprising detail is a near universal property of getting up close and personal with reality.
Yes, it's a marvel how the world functions at all. I speculate even a simple toothbrush is a result of coordination between dozens of supply chains. Even a safety pin is a marvel of engineering. Of course, it can easily be explained by humans' ability to specialize and coordinate in really large numbers. Yet, it doesn't take away the fact that how far we have come.
[1]: http://johnsalvatier.org/blog/2017/reality-has-a-surprising-...
Honestly, I can't help but judge either the company or the author. What kind of project ends up taking more than a year to complete? Wait... it's "a year longer than I’d originally projected." So what was the original estimate? Six months? It doesn't matter how complex it was. If it is taking that long, the project should have been a smaller piece of what was planned.
The author talks about re-estimating, communicating early, and owning up to your mistakes, which is all fine advice, but what if the project itself was too ambitious, and too broad to have a reasonable estimate?
Things have changed now. People have started realizing the problems with such approaches. As soon as you grow beyond the experimental stage, you start running into more issues than what these solutions claim to solve. It's cool to create a simple backend without writing code/less-code, but what if you want to incorporate an integration? caching? mail-server? background jobs?
I am old enough to remember Meteor.js, too. A JS framework that raises millions and it was about writing real-time applications with a single codebase. It met the same fate. Felt into oblivion in a few years after the initial hype.
Pardon my pessimistic take, but I see no future for a different language taking off, no matter how high-level primitives it offers. The network effects are too hard to overcome. And honestly, a language, even if mediocre, can implement the same thing via libraries.
This is the exact reason I built TextQuery [2], which solves a similar problem as OP's. I just wanted a simple app where I could drop a CSV and start SQL querying it, without creating schemas or writing code/commands.
You get into the zone because you're obsessed with a problem or an idea. It's the key to being in the flow. Too many people try to optimize the environment, when it helps only a little.
Unfortunately, I only have a little clue how to trigger it. But I do know that what you're working on is the most important part. In addition to that journaling, reading, and meditation help. Other than that, it's okay to leave these things to chance and not try too hard.
> Knowledge is an expiring asset, you might remember a few things now, but, slowly gradually, you’ll be at a point where you remember nothing of it and it’s just like you never read it. In which case, when you need that information you will go and read it and you will then, read more documents around the subject, you will be in the context that’s why you’ll remember it(for a long time).
This is a really bad assumption. Sure, you won't remember most of it, but a few ideas here and there are enough to store a hook in your memory which will be useful when you need the knowledge. Like, I have only a very superficial idea about color theory, but I do recall a long, well-written article on the subject that I read here on HN. If I do regain an interest in the subject, I will search and read it again, and the knowledge will come back to me more efficiently vs if I had not read it at all.
Chris's proposal was a wild shot, but I do think the best way to move forward is to write-off the acquisition and either give it away or sell it. Otherwise, the site risks dying out slowly.
> The logic doesn’t go away. Just because a decision is embedded into the wiring of a Zapier rule doesn’t remove any of the burden of maintenance / correctness.
Of course, AI is a lot more powerful than no-code, but the "End of Programming" suffers from the same delusion. If AI can reliably make every decision around engineering, design, and product, it would be capable of doing every task in the world. It's surprising that so many engineers believe writing things in plain text would obviate the need to learn programming.
[1]: https://www.alexhudson.com/2020/01/13/the-no-code-delusion/
> I hadn’t even completely caught up with the intricacies of Grid Layouting, when subgrid and container queries were shipped. Several of the newly added properties handle cases so specific that I hardly believe I would ever use them (hanging-punctuation and font-palette, for example).
> Here’s more: there are at least three properties related to hyphenating paragraphs. You might have used the filter property, but did you know that it supports an entirely different class of filters using SVG? Or that you can tweak the image scaling algorithm? Or border-radius support elliptical corners?
Of course, you can say that about any technology, but CSS is different. It handles too many things, in too many ways, and changes too much, too fast.
[1]: https://shubhamjain.co/2024/02/19/css-impossible-thats-okay/
1. Generating config files: Eg, Webpack, Docker-compose. Describe your use-case and it will generate the config file you need. This is usually faster than perusing docs and looking for specific flags/options.
2. Generating CLI syntax: jq, cat, tar, find. The flags/syntax are so hard to remember when you want to do something specific. ChatGPT does a great job here in quickly generating the command you want.
3. Solving problems when you're stuck: When I feel stuck with a problem or an error message, ChatGPT has proven to be an invaluable resource. Even when the answer it gave was wrong, a little hint in there was enough for me to find the solution I needed.
4. Generating functions you're too lazy to write: Often, you know how to write a function but you're too damn lazy to write it. Eg, use axios, go to this URL, get the contents and write it to CSV. Writing a function to do this feels like a chore. ChatGPT is a helpful assistant in this case.
Overall, I think there are plenty of ways the tool can save you time, even if you're skeptical about changing your whole workflow.
Netlify has multiple options to solve the problem: billing controls, request throttling, setting bandwidth limit, and waving of overages if it was a genuine DDoS, but it doesn't seem they are interested because that'd be like killing the golden goose. Just look at all the things bunny.net CDN offers [2].
It's disappointing how we acquiesce to explanations of cloud providers that are motivated by nothing other than greed.
[1]: https://answers.netlify.com/t/limiting-bandwidth-traffic-to-...
[2]: https://support.bunny.net/hc/en-us/articles/360014190440-Und...
I don't think there's much point in theorizing how it could've offered an evolutionary advantage, because even if ADHD existed at that time, it would be very, very different from what it is today.
As a creative person, motivation is a wild beast for me. Once I lose it for a project, reviving it feels impossible. But the mindset is a bit troubling. I don't think I would ever work on a project long-term working this way. So, while it's okay to abandon your side-project, it's important to make a mental note of why you're abandoning your project and if you can work on something better next time.
If you want to use anything other than VS Code as an editor, why not pick something based on native technologies? What's the point of picking an editor that takes 6-8 seconds to start and still is way behind VS Code in terms of development?