alexmorse

Supports importing from evernote, you pick the storage mechanisms, and can support e2e encryption.

I actually get pretty annoyed when it's conflated with product debt. I don't know if that has a real definition, but for me that's where your market/audience has grown to need things you did not envision/never built. This is often labeled as tech debt, even though it has nothing to do with your coders. This is an organizational issue, and one I haven't fully conquered yet.

Tech debt should not be accruing every week, it should be a conscious decision. MVP's are riddled with tech debt, intentionally. You want to get the thing out there and start gathering feedback/information, you acknowledge you don't know the right thing to build, and will do so once you have more info.

I'm also annoyed at the junior dev that doesn't take time to understand a system, and shouts that it needs to be re-written. Most times that's just because the dev is junior, or lazy. It's actual tech debt when the system is too convoluted to understand, or you haven't documented.

I have no idea what "sprint commitment" or "manager's power" are supposed to mean. They both sounds kinda sick.

If you know a rewrite is going to be a time sink and catastrophe, why on earth would you do it? Also sounds sick.

Your org should be focused on business results. If you're focused on optics, things are not healthy.

You are not in a race with your competitors unless you're in a market that is itself racing to a commodity. This is a business strategy problem vs an engineering one.

Technical debt seems far less a problem to me if you have a moderately capable software engineering team. It happens, yeah. But as your experience grows you know the proper balance of paying it down vs new work. It comes down to measuring quality of your services from an end user perspective vs how much work on engineering and support teams to maintain the desired quality.

~7-8 years cto'in

Things like: lightroom, sketch, omnigraffle,

Your email client looks very well done! Doesn't apply to me, but if I had to use outlook/office 365 I would probably snap it up.

Basically this is pedantry around something that completely does not matter. Every major registrar already provides mechanisms for hiding this info from the general public should you choose to do so.

Seems like lawyering for lawyering's sake. When can we get rid of that?

I've never bought anything from one, but I assume that if they didn't still work, I'd stop getting them.

What challenge is this addressing, what problem does this solve? Is there a problem to solve here?

I do assume there's a good reason for this, but as presented it seems like a very stupid waste of money.

What's the thing that keeps your interest? What's the change that makes you uninterested?

If you don't want any crunch, seeking out a clock-puncher position at a big corp that does some software development might be a good idea... but that will be MORE boring.

Or... start your own thing that is aligned with your interests?

Prior to 2015 any facebook app developer could make an app that had a vague one-prompt ask for permissions that gave them nearly everything, and a ton of information on friends.

Can we retitle this post "Shame: not a thing anymore"

Talk to your boss. If you feel strongly it needs to be done, explain why, and what the benefits are. You need to be able to quantify and qualify this so do your homework and sell it.

Contrived example: Hey Manager, we've broken this experience 12 times in the last year, so I'm writing unit tests for it, so we can't do it again without knowing. It will take me an extra few hours on this issue but the payoff should be worth it. I think we should do this for everything.

In the meantime, leave everything you touch better than when you opened it. Start teaching the practices you want to see.

That's how negotiations work guy.

"The Abnormal is Not Courage"

The Poles rode out from Warsaw against the German tanks on horses. Rode knowing, in sunlight, with sabers, A magnitude of beauty that allows me no peace. And yet this poem would lessen that day.

Question the bravery. Say it's not courage. Call it a passion. Would say courage isn't that. Not at its best. It was impossible, and with form. They rode in sunlight, Were mangled.

But I say courage is not the abnormal. Not the marvelous act. Not Macbeth with fine speeches. The worthless can manage in public, or for the moment. It is too near the whore's heart: the bounty of impulse, And the failure to sustain even small kindness. Not the marvelous act, but the evident conclusion of being. Not strangeness, but a leap forward of the same quality.

Accomplishment. The even loyalty. But fresh. Not the Prodigal Son, nor Faustus. But Penelope. The thing steady and clear. Then the crescendo.

The real form. The culmination. And the exceeding. Not the surprise. The amazed understanding. The marriage, Not the month's rapture. Not the exception. The beauty That is of many days. Steady and clear.

It is the normal excellence, of long accomplishment.

-Jack Gilbert

Set aside DND time on the calendar where your team knows that you are not to be interrupted unless the servers are on fire.

I have to break projects apart into smaller pieces so I can show myself I'm progressing towards the end goal and not just stuck on a treadmill.

Once started, it's much easier to keep going. This applies to just about everything I can think of. Take the first step, build momentum.

Having goals or soft deadlines helps too. Tell a friend you're going to show them progress by a certain time.