General Availability of Amplify UI for React
1 points • 0 comments
@kevinslin | Hacker News
From 12/27/2013, 11:59:06 PM till now, @kevinslin has achieved 947 Karma Points with the contribution count of 229.
Recent @kevinslin Activity
yep
happy customer of gitjournal. also creator of a git backed open source note taking tool. we don't have a dedicated mobile app (yet) and recommend folks use gitjournal > https://blog.dendron.so/notes/fDCVPEo3guCFWPdxokXHU#gitjourn...
reminds me of the trend to containerize/micro-service/lambda things for *scale* - its usually just introduces unecessary complexity
used to work at AWS where I've worked with (and created) legacy services that failed to scale with rising usage (a good problem to have). Its not that these services were badly designed - rather, they were designed to meet the scale and constraints at a point in time. And that's okay
The future is hard to predict - so make it easy on yourself and solve the actual problems you have today vs hypothetical ones that might never materialize.
Especially in tech, by the time you do need to solve that problem, there will probably a better (serverless AI blockchain) technology that you can use to do it
Quit Your Job
4 points • 0 comments
Notes on the Art of Learning
1 points • 0 comments
My Notes on Hooked
1 points • 0 comments
you might also want to check out https://dendron.so It's like notion but for developers and embeded inside of vscode (disclaimer: I'm the founder)
The problem with externalizing information (note taking) is that past a point, it becomes difficult to find information again when you need it (because you have too much information to comb through). wrote extensively on this in [It's Not You - It's Your Knowledge Base](https://www.kevinslin.com/notes/e1455752-b052-4212-ac6e-cc05...)
I find that at the end of the day, the only thing that works over long periods of time (and a large number of notes) are hierarchies with a regular structure that can be applied consistently. The pain point with this system is that hierarchies are hard to change and the way we think of things does change. This is why I ended up creating my own note taking tool built around the idea of flexible hierarchies (https://dendron.so)
Articles like this often inspire wishful thinking (aka - if I bookmark this page or highlight its content, I know have access to all the mental models).
I find mental models like knowledge in general - useful only if you can find the relevant entry *when needed*. They're not useful if just collected on a shelf but ingrained into memory and lived as everyday live. That being said, first step of ingraining useful mental models is to write them down (hence, [my mental models](https://kevinslin.com/notes/LMpLWbLBIfRzkSjJlF7U1)).
Amazon EC2 M6id Instances
2 points • 0 comments
Thanks :)
I like to have a fairly regular routine with consistent time to wake up every morning. The typical day is divided into four phases:
- morning: start of with yoga and focus on most important work before noon - noon: take a breather with running, have lunch and read up on hacker news - afternoon: more work, mix in nap and meditation to get through the afternoon - evening: wind down, prepare for next day
You can find a detailed breakdown [here](https://kevinslin.com/notes/qm4lvh7xusf8tufke30gr2q)
Zettelkasten was a tool designed for a very specific purpose but of late, is the proverbial hammer that is being applied to everything. As the founder of a note taking tool (dendron.so), I see lots of new users trying out PKM for the first time because they heard about zettelkastenw hen all they needed was a bullet journal instead.
This is my first time coming across LYT - thanks for the writeup!
The remarkable story behind Beethoven's “Ode to Joy”
2 points • 1 comments
On Suffering
2 points • 0 comments
what do you mean by overhead? do you mean performance or complexity?
nice writeup!
i'm currently working on shipping the publishing side of dendron in a docker (its a custom nextjs app) so that it can be easily tested locally as well as hosted remotely
that's fair. the dot hierarchy has been a polarizing topic with folks falling on both sides of it.
the reason we went with it is because: - it allows a file to be both a note and a parent of notes - it makes hierarchy an explicit part of note creation - it greatly simplified operations like refactoring (regex over filename, no need to create scaffolding with empty folders or removing folders if they no longer had children) - it makes it easy to work with using cli tools
More discussion on this here: - https://wiki.dendron.so/notes/683740e3-70ce-4a47-a1f4-1f140e... - https://wiki.dendron.so/notes/683740e3-70ce-4a47-a1f4-1f140e...
the reason we have our own extension is because dendron is also available on vscodium and the `paste image` extension was not available there
site design / logo © 2022 Box Piper