Hacker News new | past | comments | ask | show | jobs | submit | mystickphoenix's comments login

Just wanted to say you've built an amazing product. So much so that I got my team hooked on it and am working on getting it out to the rest of the company that needs it. Well done!!


I noticed it’s open-sourced, right? How do you avoid people coping the code and running by themselves?


Currently use markdown files + dropbox for sync. I can't seem to stick with a single notes app for any appreciable length of time but having files in plain text makes it easier to switch.

Currently using:

- Obsidian: this one has stuck the longest

- iA Writer: really pretty, seems to be more useful for longform

- NeoVim: I live it in anyway... may as well

- rlg: my own "dump thought to single file w/ timestamp" rust app), very janky, written specifically for my own use-case, standard "there may be dragons here, might eat your computer just for fun, etc" - https://github.com/bryan-lott/rust-lab-log


Taking the opportunity to plug my favorite blog post ever:

"the truth is everything is breaking all the time, everywhere, for everyone"

https://www.stilldrinking.org/programming-sucks


Add another vote for mise. For me it replaced asdf, pyenv, poetry, and direnv. Biggest thing for me is it _just works_:tm:.


Someone else already mentioned Autism and ADHD, possibly a combination. Those would be my first guesses. Another one is potentially migraines. They aren't always "a bad headache" as they tend to be portrayed but can run the gamut of symptoms. From nausea, to sound/light sensitivity, to temporary blindness, or actual pain.

Definitely sounds like something you'll want to investigate with a doc, assuming you have access to one. Biggest thing is if possible, shop around until you find someone who actually seems interested in what you're experiencing and doesn't dismiss your symptoms.


I use Amethyst https://github.com/ianyh/Amethyst in my day to day. Slightly different management philosophy but one that works well for me.


Reminded me of a tool that I created and use daily (and that I need to get back to adding some functionality to!) Among the things I need to do are... add a readme! But it's a low friction (for me) way to keep a log of what I've done. Basically just a digital notebook, inspired by the lab notebooks I saw whenever I went to my dad's chem lab when I was young and what we like software to do when it changes something. Keeping a record of what you've done has been incredibly helpful for me and I've gone back and referenced it many many times.

I happen to write in an obsidian-friendly markdown syntax but it's not enforced. Day and year headers are added automatically and each entry is timestamped.

https://github.com/bryan-lott/rust-lab-log


I reread this every so often to remind myself as a software engineer that yes, we're all crazy, we're all driving ourselves a bit more crazy all the time, so give myself (and my coworkers) some grace.

https://www.stilldrinking.org/programming-sucks


For me learning Rust isn't about "OMG this is my #forever-language", it's more about presenting me with a new way of thinking about and through problems. I code 99% in Python at my day job and when I made the effort/struggle to learn Clojure a few years ago it fundamentally altered how I think about problems. This is the same result I'm looking for from Rust. Basically just adding more tools to the mental toolbox.


It will not be as big a change in thinking as Clojure, I am quite sure, but the type system usage is where the change will comw from. That and perhaps borrow checker.


If you haven't already, I'd add Nonviolent Communication to that already very good list!


is this the book you'd recommend?

https://www.amazon.com/Nonviolent-Communication-Language-Lif...

a cursory search online already makes this look absolutely awesome! I'm totally adding this to my repertoire

honestly, i work in public education and I feel like these kinds of negotiating and communication skills could easily be a doctoral dissertation


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: