izuchukwu
Joined 9 years ago
Karma
243
Submissions
55
Member since
Dec 30
https://izuelechi.com
View on Hacker NewsRecent submissions
Comment · 4 days ago
A consultant at McKinsey is drafting the slides pitching this as we speak
Comment · 1 year ago
Had the chance to see one of these in person - did not believe you could achieve “daylight indoors” before I did.
Comment · 2 years ago
It was most likely Subset: https://news.ycombinator.com/item?id=36894939
It appears they are re-engineering their product, as they've taken down their sign up link and their landing page now advertises an upcoming, more traditional spreadsheet product: https://subset.so/
Their docs are still up, however, and has screenshots from their old infinite canvas spreadsheet product: https://docs.subset.so/
Comment · 3 years ago
You should check out https://brev.dev. You can rent GPUs, pause instances, use your own AWS/GCP accounts to make use of your credits, and the CLI lets you use your GPU as if it’s on your local machine.
Comment · 4 years ago
Check out the Creativity Faucet by Julian Shapiro. It’s a brief take on the same phenomenon: you’ve got to let the tap run and let the wastewater out before getting to the good stuff.
That’s because, in part, the good stuff is made out of identifying why the wastewater fell short.
Comment · 4 years ago
If you want to get starting building with AI right away, I'd recommend getting an OpenAI key and playing with prompts in a tool like Everyprompt. Start asking it whatever you can think of, click Deploy to make an API out of it, then try building apps based on that.
You can then try running Stable Diffusion and using that in your apps too.
These other answers, while well meaning, are for building models and not for practically working with AI. They're like being given resources on how compilers work when someone asked how to write "Hello World."
Once you get that magic feeling of having something working, you can always dig into all of the research, like https://course.fast.ai, later.
Comment · 4 years ago
If you've chosen the right data structures and organized things well, the interfaces will be self-evident too.
Comment · 5 years ago
There are ways to specify schemas for JSON and XML. However, for APIs, XML's gone and schemas for JSON never caught on.
JSON is a serialized JS object, which itself is untyped, so anything can be in any order. Think NoSQL databases. This simplicity gave JSON the ability to be adopted by a multitude of languages very, very quickly. Foolish, maybe, but you could build Stripe on it.
GraphQL, an emerging API standard, does feature schemas, and its rise is bringing types back to APIs. It can be a bit more work to implement than JSON, though.
It's the classic complex-simple-complex pendulum swing. We're not done, either.
Comment · 5 years ago
The computer doesn’t have to do these locally—there’s no reason this couldn’t be implemented as a thin client.
I agree that data has to be converted, but I don’t agree that it has to be as manual as it is today. Consider this: In addition to your API, a second JSON file gets generated that describes the schema of the first. On the consuming developer’s end, their language & IDE uses that schema to let you call APIs or RPCs exactly like they were local functions.
Comment · 5 years ago
A big issue there is accessibility to a broader audience—something that Emacs and Lisp Machines don't quite have. Like you said, iOS Shortcuts is a very interesting example. You could say Internet-native automation tools like Zapier and Integromat fit the bill here too.
I wouldn't see potential maintenance or QA work as a deterrent to mainstream adoption. Users would underestimate it just like developers today do.
Comment · 5 years ago
Listening to his recording of the subthalamic nucleus—as he describes it, "the sound of hundreds of thousands of your own neurons excitedly relaying the information they carry to one another fill[ing] the room"—was worth the read alone.
Highly recommend reading this post.
To the author: thank you for sharing, and I wish you a successful course of treatment.
Comment · 5 years ago
Generational leaps emerge in the same ways everywhere.
For any space, if you provide a large enough net win for a large enough number of people, you introduce a generational leap. Very often, those people are completely new to the space.
The measure here isn’t how many growing companies that started with no-code adopt code as they grow. The measure here is how many growing companies that started with no-code wouldn’t have been started otherwise.