I'd be up for a meet, do you have a preferred email or messaging app?
3,211 karma · joined May 2, 2018
See what I'm up to: koljasam.com / blog.koljasam.com
Also feel free to contact me: hi ( at ) koljasam.com
I'd be up for a meet, do you have a preferred email or messaging app?
Nit: I think that when an exercise was just attempted, it should not come up immediately again (soon, yes, but w/ some enforced delay, maybe) — otherwise it feels a bit tedious (even though it's probably decent for internalizing it)
- stack A needs lots of tedious, not-quite boilerplate not-quite-copy-paste work whenever you implement something, but reduces cross-OS bugs, UX and accessibility issues down the line. Lots of dev frustration, slows down iteration (when humans actually have to do this).
- stack B has awesome DX and affords smooth operation of the design/UX/dev teams, very fast. More issues down the line, though. May be worth it if unaided humans need to work on it.
If you're looking for feedback: It's easy to get started (pleasant that you are not forcing a login), but not so easy to understand what to actually do — what's the main flow? Which buttons am I supposed to press to do what? Some onboarding may help.
Since I'm not really in the market to learn English: Are you planning to offer this for other language pairs?
yeah if it's no effort, please share, otherwise I reckon I'll rebuild it myself some time soon :)
I'm a bit too beginner to effectively use the app, sadly, but it's quite an interesting flow.
As an aside, a while ago, I sort of prototyped the reverse: Learn vocab to understand a natural language sentence, translate the sentence (https://infi.koljasam.com)
Happy to talk and exchange notes, if you want :)
I think this has been my biggest hurdle with LLM-based learning, even though I think the concept may be quite powerful...
Happy to hear more about your approach :)
It seems to be simply a great idea...like...should we bring it back? Could we?
- Doing anything usually involves prep work. Want to take a step? First put on your shoes (literally or figuratively, depending). If your attempted habit is 70% prep, your brain will somewhat rightfully conclude "this is stupid" fairly quickly.
- "Just do X every day for [long time period]" has an inherent falsification problem: You aren't "allowed" to argue against it until you tried it. Stopped after 2 years because you saw no change (and 5 was recommended)? You are still not allowed to argue against the strategy!
- You can actually make steps so small that they're useless. I once set out to have (at least) one github commit online per day (going for that green tile!). This led to my brain finding hacks like rephrasing one sentence of an old blog post. Doing that for 20 days is way less effective than one single coding session, at 20 times the emotional cost.
- Doing something daily for a long time is extremely hard to achieve, especially if it's not the main thing you're doing. It's rare in the wild. You will find piano virtuosos who play piano daily, but not piano virtuosos who also go to the gym daily.
Code is an abstract way of soldering cables in the correct way so the machine does a thing.
Art eludes definition while asking questions about what it means to be human.
Of course you could always find opinion pieces, blogs and nerdy forum comments that disliked AI; but it appears to me that hate for AI gen content is now hitting mainstream contexts, normie contexts. Feels like my grandma may soon have an opinion on this.
No idea what the implications are or even if this is actually something that's happening, but I think it's fascinating
I find it a powerful mental model precisely because it is not a statement of success rate or survival rate: Yes, a lot of ideas never break any kind of viability threshold, sure, but every idea that did also started out as laughable, toy-like, and generally shit (not just li-ion batteries, also the wheel, guns, the internet and mobile computers).
It is essentially saying 'current lack of viability is a bad indicator of future death' (at least not any more than the high mortality of new tech in general), I guess.
Pretty shoddy brick walls (just straight blocks), crumbling at many places, constructed possibly along ancient foundations or maybe not, that you sort of walk through. Interesting things here and there. Couple of other tourists.
Walking through Saddam's palace next to it was much more fascinating; extreme grandeur morphed into a typical lost place with graffiti and empty bottles. The nearby town Al7illa certainly offered more to actually experience, like a mini theme park with the main attraction being (artificial) rain.
Anyways I genuinely wish the committed people all the best in the restoration, but I feel like the article is a tad over-enthusiastic and easily convinced.
How will you collect the data (about me)? How much? How much more individual will this be compared to just subscribing to my city's newspaper (or a trade magazine, if we're talking job-related news)?
This may be just me, but I also think collecting emails here is a really weird first step — most news services provide at least a blurb of each article w/o any kind of signup, so this broke my expectation in a "what do you need my email for" kind of way.
Hope that helps.
If I hire you to make software for me, I don't really want software; I want a problem to go away, a money stream built, a client to be happy. Of course, that probably requires you to build software, unless you invent a magic wand. But if you had the magic wand, I'd choose it every single time over software.
Not so with food, furniture or a fancy hotels, where I actually want the thing.
There is no inherent value to producing software, as there may be in producing car tires or bananas. The best software is no software.
And then who is the better programmer, the one who knows more about how to make software, or the one who knows more about what software to make?
I wonder about this often: If you want to have impact/solve problems/make money, not just optimizing killing your JIRA tickets, should you invest a given hour into understanding the lowest code layer of framework X, or talk to people in the business domain? Read documentation or a book on accessibility in embedded systems? Pick up yet another tech stack or simply get faster at the one you have that is "good enough"?
Not easy to answer, but worth keeping in mind that there is more to programming than just programming.
I think this could really benefit from lazy signup, a demo directly on the landing page, or at least way more screenshots.
Given that making a checklist in my notebook or established organization-app of choice is almost 0 friction, signing up or downloading an app feels like asking a lot without seeing the clear benefit 100%.
Good luck with this :)
I just started getting into ko-fi, and I'm wondering from a content creator perspective in which cases your product should be my choice over the classic players (patreon, bymeacoffee, ko-fi). Good luck tho :)
Some feedback: I'd love some simple usage examples. I'm a newbie to the space of i18n, and your documentation goes from the installation (simple enough) to a fairly fat boilerplate to put in my app.js, without communicating how the actual workflow will actually look like.
Maybe I'm not your target audience, tho...