[bingo_cannon]

I was overwhelmed at first. Every time a Show HN would pop up, I was amazed at how individuals could deliver on so much alone. So I accepted these things:

- There will always be people who are better than you, in any field. I see it as a positive and a great learning opportunity.

- There will never be time to learn everything you want to learn.

The question I try to answer is: Am I doing the best I can at the moment? Of course, this can also lead to complacency.

[codyb]

And then you need to realize that if you spend a bit of time every day doing a little something, you'll be able to deliver some pretty big things over time.

The hardest part, I find, is starting. But once I do, boy is it a lot of fun to keep that ball rolling! There's nothing so enjoyable as hacking away at something and seeing those incremental changes fall into place.

[jacquesm]

> The hardest part, I find, is starting.

To me the hardest part is finishing. To start stuff is very easy for me but to actually grind away at something day after day until it is finally done is very hard.

[codyb]

Thanks for saying this Jacquesm. I've read several of your articles over time so to receive unexpected correspondence from a respected engineer is, to say the least, very cool. You're absolutely right.

I find that one of the biggest contributions towards my feelings of burnout is the fact that, when it comes to software engineering, not much is ever truly finished. A lot of us work for places where the product is never actually finished.

When we work in environments where there is always another ticket to complete, it can be hard to feel as if there is actually an end in sight to much of anything. My father is an accomplished woodworker/graphic designer/renaissance man, he's built things such as book cases, stained glass windows, picture frames for his gorgeous nature shots taken across the United States, and even (when I was younger) a cedar stripper canoe.

Sometimes I very much long for the feeling that he has when he has completed a project. One he can run his hands along. We're not afforded that luxury as software engineers. We work on some of the most complex projects ever to be known to man. Projects with millions of lines of code that are never truly secure, complete, or tangible. When we step away from the keyboards, there is nothing in meat space which exists as proof of our work.

That being said, when I have the pleasure of working on my own terms, in my own office, I find nothing more satisfying than hacking away at my own projects. I am not sure if that is true for every engineer but when I have the luxury of being able to spend a couple of hours researching Git branching strategies because that is something I think will not only make my project more maintainable but me a better engineer, I just love it.

I am consistently humbled by our profession. Every single thing I'm assigned to seems to me to be easy in my mind, and it absolutely never is. (Of course I refuse to stay comfortable and take on everything I can).

I guess at the end of the day, if you don't enjoy the journey which may never end (and is more likely than not to be endless), it may not be the field to devote your time to. But if you can enjoy being constantly overwhelmed by the myriad of options for your development environment, databases, servers, and front end frameworks, then there really is nothing so sweet as hacking away at a project you can call all your own.

[jacquesm]

I actually try to teach the companies I work with. I call it 'never ending ticket queue syndrome'. What I try to tell them - and which usually clicks - is that the ticket queue is not supposed to be a tredmill, but a series of roads going to an intermediary spot where you can get off the road for a bit. The shorter the ticket queue (or at least the visible portion of it) the better. Sticking your 12 year product roadmap and a couple of hundred unsolved issues the majority of which will likely be forever pushed back because of higher priority items in a company wide visible queue is an excellent recipe for burn-out.

[losteric]

The internet solved discoverability but gave us the problem of consciously avoiding information, learning about the right things at the right level and accepting some ignorance in favor of specialized deeper understanding.

Personally, I forward everything from HN's front page, every tech-relevant subreddit, major tech companies and software projects, roughly 30 blogs, Twitter, and blogs/changelogs for every project/service I depend on (for work or side projects)... all straight into my email.

Rules automatically curate emails into prioritized / categorized folders. Setting up those rules was my solution to information overload - reviewing rule relevance is the same as measuring how my attention investment tracks against long-term learning goals.

One process for managing my work, personal life, and interests :)

10 minutes a day is enough to follow every personally relevant development. I do a deeper hour-long review of lower priority content at least once a week, but my email is an effectively infinite backlog of interesting-possibly-relevant information.

[ferdterguson]

> I do a deeper hour-long review of lower priority content at least once a week, but my email is an effectively infinite backlog of interesting-possibly-relevant information.

As a zero-inbox kind of person this is terrifying. It's already enough effort to keep up with the new journal articles every day. I use my morning commute to do that and my evening commute to unwind and read the more interesting stuff.

[losteric]

I don't think you understand, my inbox is almost always at zero :)

This folders and rules was my strategy for balancing the need to be hyper-informed, well-organized, and not-overwhelmed... only uncategorized content shows up in my inbox.

My "High Priority" folder has subfolders for friends, family, bills, and other things that have to be kept at 0. The "Low Low Priority" folder has folders for online store emails that useful a couple times a year for discounts when I need a new shirt or something, auto-deleted after 14 days. In between is everything, nicely triaged and categorized.

It's really more of a personalized private ad/tracker-free mobile and cli-compatible individual media aggregation service - perfectly managing the flow of the internet into my brain :)

[i336_]

So, I'm trying to do what you do, entirely using browser tabs. It concretely doesn't work.

After 200-400 suspended tabs open and a browser chewing molasses, I tend to export all URLs to a list for One Day In The Magical Future™, kill my session and restart.

So yeah, I'm very interested to find out what rule system you use - is this bespoke, or using standard email client features?

Also, what email client do you use? I've been trying to find a medium between "old computer becomes unusable after >10 tabs are open" and "fast, native information-presentation applications (like terminals) are text-only and don't support images" for 15+ years.

I use Gmail's basic HTML mode 99% of the time. It... I can't say I like it. I want something that doesn't use Qt and GTK+, because I perceive more lag with applications that use these toolkits than I did with lightweight WinAPI apps I ran on Win98/Win2K machines with half the hardware capability.

[losteric]

Browser tabs were a different part of the puzzle, for me anyway. This is my preferred way of managing information:

* My email pulls new information into my digital sphere of awareness. * Browser tabs/history manage active context and mid-term working memory. * Bookmarks (poorly) curate resources for long-term information retrieval. * My git-backed repository of notes tracked my own thoughts and plans.

Fastmail, gmail, and my old university Outlook account all support creating rules, however I am not aware of any RFC standards around rules. My adhoc suite of scripts for pushing content to email is entirely custom.

I like Thunderbird, but it's a pig at 300MB memory consumption... however it's open source and does what I expect.

[chrismorgan]

Sieve scripts (https://tools.ietf.org/html/rfc5228) are the standard for email rules; FastMail uses Sieve scripts internally and also allows you to write your own if you desire: https://www.fastmail.com/help/technical/sieve.html.

[navalsaini]

I would love to read an article on setting up such rules. Any links to posts?

[losteric]

Unfortunately, setting up rules is very client-specific. Fastmail, Gmail, and Outlook all have different UIs.

[yeswecatan]

Complacency may be a blessing at this point. For years I had the mindset that it's a bad thing.

[gorbachev]

Do what makes you happy / keeps you and your family fed.

If complacency does that for you, then it's good. If not, it's not.

[RugnirViking]

> Do what makes you happy / keeps you and your family fed.

The issue is for many people these two seem to be opposites

[kinleyd]

Pith instruction. I don't think it can get much more succinct than that.