600frogs

From reading the other comments here, I have to say I think a single file may be easier to work with than the one-file-a-day we're currently using. For example, it'd be much easier to skim through a single file for the month/year/whatever and pick out the highlights than going through each file individually.

Anyway, love the highlights idea, think I'll be pinching that!

RE: Why track, I think it's for both:

* I want to be able point to past achievements and see the value I'm adding (both for personal well-being and also CV writing/interviewing)

* I want to be able to see what I've done in a day/week/month/quarter to see if I'm performing well and delivering what both I and (potentially) my manager expects.

* If asked why X hasn't been done yet, I want something concrete to point to so I can provide my reason, without fumbling around for excuses or reasons I can't remember.

Is there any reason you chose RTM specifically? I happen to use Bear for my daily notes, but I'm wondering if perhaps just a to-do tracker (Kanban, RTM, whatever) and a single achievements.md file might be better.

Agreed on low-tech, low-tech can be great! My personal calendar is just a huge whiteboard I scribble on, and redraw at the end of every month. Physically crossing out tasks/appointments is rewarding in the way that a phone-tap or CTRL-X CTRL-V can never be.

That being said - do you not find the duplication of tasks from the index card to day.md to be annoying/unnecessary? I know if I was rewriting the tasks from the index card to the .md file every day I'd get irritated and eventually just resort to the .md file, but maybe I need to learn to be a little more patient :)

I love the idea of a changelog, but that only works well if you're working on a single system for a long period of time - the nature of my work means I'm hopping between systems fairly frequently, so a changelog doesn't quite fit the bill for me. Sounds ideal for your work though - and I really appreciate that twitter thread, great work!

Agreed with matt_s - if you're looking to be distracted, just accept that and do something genuinely entertaining e.g. video games, YouTube, rather than finding some other forum with half-baked opinions to idly browse. And yes, I'm being hypocritical by posting here, but I count HN as part of my keeping-up-to-date-with-tech diet, which makes me feel a bit better about myself.

In an ideal world using whatever ticketing system your company uses would be great, but I find in practice a significant amount of the work I do is untracked - attending/scheduling meetings, catching up with X about Y, etc. In theory all work should be trackable, but I find it doesn't make sense to keep these smaller, "personal" tasks logged company-wide.

RE: keeping the DONE list, for me it's not about knowing exactly what I did at 11am on date XX/YY, but it's more about proving both to myself and the company (if asked) what I've provided/achieved, and to hopefully be able to better understand my rate of work (this one is still a WIP - I haven't done any analysis yet and doubt I ever will, but it's nice to know I could!)

Ah if the files are in version control you're golden, but for personal tracking using a git repo seems a bit overkill and not frictionless enough. The email idea isn't bad though, simple and effective!

I used Trello for a period of time, and the manoeuvrability (if that's the right word) of it was great - shuffling priorities around in a list, the satisfaction of dragging to a DONE column - so for tracking current tasks it was great. However, it was unusable for tracking and saving previously done tasks - they'd just pile up in a big DONE column, and eventually I'd have to archive it, losing all tracking. Have you solved this particular issue, or does accomplishment tracking not rank high in your priorities?

Interesting - it sounds fairly similar in terms of cutting plaintext TODOs into a DONE list, but with greater visibility on a macro scale. Do you never date anything in the DONE list though? I might have a hard time remembering when I achieved big milestone X, or how long problem Y took to solve, which is part of why I want to track my work.

Have they fixed the iOS jank yet? I was looking into this a few months ago, but at the time the demos coming out for iOS were appalling, so I dropped it.

I've never fully committed and built a solo product, so take what I say with a large pinch of salt, but from what I understand asking your friends "would you buy this" is supposedly a notoriously poor metric for market fit. Their answer is always going to be "of course!" because it's easy and it seems supportive, but the difference between "would I spend this hypothetical money on this hypothetical product" Vs spending real money is huge.

You've missed the point of a shotgun - DPS is irrelevant, it's how fast I can get you to 0 before you can get me to 0. And shotgun wins there, at least up close.

> After about a year, atoms from your candle will have spread completely around the globe.

How on earth is this provable?

My instinct would have been that it's easier for the submitter (as they have less to polish and test) and more irksome for the reviewer as they have to go through multiple rounds of submissions, but naturally I'll take your word for it!

This kind of discussion is always of interest to me, I'll check out the book, thank you.

I did read through this debacle when it came out actually, I'm thoroughly on team Greg. I suppose my question was separate from malicious patches - I was interested in knowing if this incremental "merge tiny patches as and when they're ready" mode of development has ever caused issues with half-baked solutions affecting other parts of the kernel where perhaps it wouldn't have otherwise done so if the release was given more time for polishing and testing.

So it seems to be it's primarily solving branching issues rather than providing any benefit of the incremental support, is that correct?

Interesting, thanks for the explanation. Has this style of development ever come back to bite you?

I'm not hugely familiar with the Linux release cycle, can anyone explain why such rudimentary support should be merged in now, instead of waiting until it's ready?

I'm always wary of claims like this as there's so much snake oil targeted at audiophiles that I can never tell if the product offers a genuine improvement or if it's an expensive placebo. Would you be able to tell the difference between this and e.g. an iPhone DAC in a blind test?

Meditation without yoga may be problematic, but is there any problem with practicing yoga without meditating, in your opinion?

The author suggests that if I find email horrible to work with, it's my mail client that's at fault, but doesn't expand as to why this is or make any suggestions for what to use - can anyone help me out here? What am I missing from some amazing holy grail mail client that I don't get in gmail webapp or the default MacOS mail app?

Just be sure nobody mistakes it for the .idea/ folder intellij products leave behind and deletes it!

I wonder what the Ethereum equivalent of trimming armour is...

Interesting, that might be a dealbreaker then. Have you found significant slowdowns in working in a VM vs native, both in terms of compilation and day-to-day work, or has it been negligible/unnoticeable?

P.S. thanks for making an account just for this reply :)

That'd be super great if you could let me know how it goes, I'm tempted to make the same jump. Thanks!

I did try VSCode remote running and debugging, but found it fiddly to work with and half-baked. Plus, I was sorely missing IntelliJ, so I quickly stopped trying it out - maybe I'd get used to it eventually, but it didn't seem worth the onboarding cost. The RDP and X410 solutions suggested in the replies to GP seem solid though.

Your set-up sounds exactly what I'm after - from my comment to a different reply:

> I think my end goal is to have a contained development environment whilst not being forced to use specific tools (i.e. VSCode remote debugging, eugh) and not sacrificing compilation times by running in a VM that's too slow.

Are there any other gotchas to working like this? As it happens I'm a go dev using GoLand so your go-specific issues are of interest to me. I'm not too bothered about not being able to use Windows GoLand as I'd be just using it from WSL2 anyway, but I'd be interested to know if there are any other pain points. Any issues with VPNs, if you're using them?

Thanks for the links, some interesting stuff there! I think my end goal is to have a contained development environment whilst not being forced to use specific tools (i.e. VSCode remote debugging, eugh) and not sacrificing compilation times by running in a VM that's too slow.

From the look of it, if I were to set up the WSL2 Ubuntu GUI with RDP, that'd tick all the boxes, right? And as a bonus I'd be able to access files in WSL2 from Windows.

Any idea how WSL2 interacts with VPNs? I've seen some mixed reports around the web but this is also a must-have for me, if I can't use a VPN in my dev environment it's game over.

I'm definitely interested in WSL for developing, but last time I tried it a while back (WSL2 just came out I think), there was basic functionality missing e.g. I couldn't write and run my own SystemD services. Has the situation improved since then?

When you say "proper Linux distribution", I assume that's still CLI only? Do you develop with e.g. emacs, vim on WSL, or do you have some IDE with remote running and debugging into WSL? Or have a missed a trick and in fact X/Wayland applications can be run on WSL?

Just chiming in to say I love bearblog, it's a fantastic platform! I'd be interested to know how you monetise it, or if it's unmonetised, then how you plan on doing so in the future if the platform grows past a hobby project.

P.S. I understand the "Made with Bear" in the footer is part of the growth strategy and the "price" (albeit a tiny price) to pay for getting your blog hosted, is there option (paid or otherwise) to remove this, say if I wanted to host on my own domain?