Are you guys for real? A mobile app?
Who in the world who’s interested in this would do it on a mobile app.
Show HN: Fata – Spaced repetition to fight skill rot from AI coding
31–40 of 66 posts
Re: Show HN: Fata – Spaced repetition to fight skill rot from AI coding
#32Are you guys for real? A mobile app? Who in the world who’s interested in this would do it on a mobile app.
People often do their 10 minutes of daily fata.dev during their commute where mobile/offline access is ideal. The UX is optimized for mobile but you can also do it on your computer, it's a progressive web app that is installable as a desktop app:
Re: Show HN: Fata – Spaced repetition to fight skill rot from AI coding
#33Engineering has never been, nor will it ever be, about "repetition" or "memorization." This is a relatively new fable invented by those that have participated in ritualistic interview hazing. Imo, there are, broadly speaking, two types of engineers: computer scientists, and programmers. Computer scientists do science. The end result is a new algorithm or theorem, and they work with lots of math, proof systems, formal…
Focusing on your first point: Memorization isn't everything. But it's not nothing either.
Sometimes it's nice to be able to just bang out some code without looking everything up. IDEs in an IDE-friendly language make this awareness accessible in the immediate frame, but don't necessarily help with having a mental menu of possibilities to choose from.
That said: I find spaced repetition utterly crushing, so I only use it very sparingly.
Re: Show HN: Fata – Spaced repetition to fight skill rot from AI coding
#34Great lessons
Re: Show HN: Fata – Spaced repetition to fight skill rot from AI coding
#35Great lessons
Thank you
Re: Show HN: Fata – Spaced repetition to fight skill rot from AI coding
#36Engineering has never been, nor will it ever be, about "repetition" or "memorization." This is a relatively new fable invented by those that have participated in ritualistic interview hazing. Imo, there are, broadly speaking, two types of engineers: computer scientists, and programmers. Computer scientists do science. The end result is a new algorithm or theorem, and they work with lots of math, proof systems, formal…
> Engineering has never been, nor will it ever be, about "repetition" or "memorization."
Having memory of how to do things and techniques and tools and patterns is absolutely important for solving problems. The very reason experienced engineers are just better at many classes of problems.
> This cleverness can't be augmented by AI, and it can't be rotted by AI: it's something that's innate to people
I argue "cleverness" is a learned and honed skill by exposure and exercise. I just reject the idea that some people are just incapable of original thought. They just didn't get the circumstances to flourish.
Re: Show HN: Fata – Spaced repetition to fight skill rot from AI coding
#37Engineering has never been, nor will it ever be, about "repetition" or "memorization." This is a relatively new fable invented by those that have participated in ritualistic interview hazing. Imo, there are, broadly speaking, two types of engineers: computer scientists, and programmers. Computer scientists do science. The end result is a new algorithm or theorem, and they work with lots of math, proof systems, formal…
Engineering creativity does not come from a blank slate.... people create by combining primitives like APIs, algorithms, patterns, debugging techniques, product constraints, performance constraints, user needs, and blah blah blah.
You can argue that a particular primitive is bad or overemphasized but the ida that real engineering has nothing to do with repetition, memory etc is wrong.
Re: Show HN: Fata – Spaced repetition to fight skill rot from AI coding
#38This is very, very cool! Super impressed by what you've built. As a non-programmer who is now doing a lot of vibe coding for myself these days (and feeling very scared about which of my vibe coded things will just randomly break one day haha...) I feel like what I'm missing isn't necessary language syntax skills, but rather the higher-level planning/organization/architecture capabilities that a seasoned software engi…
Have you tried to understand the code that's being produced?
That'll go a long ways to actually helping your vibe coded thing not break, and also will make it easier to change things in ways that you actually want changed instead of throwing it into the black box again hoping for the best.
Re: Show HN: Fata – Spaced repetition to fight skill rot from AI coding
#39Engineering has never been, nor will it ever be, about "repetition" or "memorization." This is a relatively new fable invented by those that have participated in ritualistic interview hazing. Imo, there are, broadly speaking, two types of engineers: computer scientists, and programmers. Computer scientists do science. The end result is a new algorithm or theorem, and they work with lots of math, proof systems, formal…
Engineering creativity does not come from a blank slate.... people create by combining primitives like APIs, algorithms, patterns, debugging techniques, product constraints, performance constraints, user needs, and blah blah blah. You can argue that a particular primitive is bad or overemphasized but the ida that real engineering has nothing to do with repetition, memory etc is wrong.
Well, the inventory of primitives has to be earned. Else they can't actually be composed. Composition requires tacit knowledge. There's a learning pyramid thing that describes it. Just asked chatGPT to jog my memory (heh, heh)
Remember → Understand → Apply → Analyze → Evaluate → Create
Discussions on learning typically bring up the need for rote learning, repetition and vocabulary building. It is essential, but to focus on it "as the mechanism for learning" does more harm than good. It's necessary but in no way sufficient.
Re: Show HN: Fata – Spaced repetition to fight skill rot from AI coding
#40Engineering has never been, nor will it ever be, about "repetition" or "memorization." This is a relatively new fable invented by those that have participated in ritualistic interview hazing. Imo, there are, broadly speaking, two types of engineers: computer scientists, and programmers. Computer scientists do science. The end result is a new algorithm or theorem, and they work with lots of math, proof systems, formal…
> Engineering has never been, nor will it ever be, about "repetition" or "memorization." Having memory of how to do things and techniques and tools and patterns is absolutely important for solving problems. The very reason experienced engineers are just better at many classes of problems. > This cleverness can't be augmented by AI, and it can't be rotted by AI: it's something that's innate to people I argue "cleverne…
> I argue "cleverness" is a learned and honed skill by exposure and exercise.
Even if I were to concede this point, it's certainly not honed by the kind of exercise that OP is advertising. We are deep in Max Howell's "invert a binary tree" territory here.