• 17 Posts
  • 238 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle

  • That’s a tough one. There’s not a ton of great options for personal accounting apps, much less self hosted ones. I used Pocket Smith (subscription based) for years which actually does what your looking for. Decent product overall. I switched from them to Quicken mostly because I’m an anal retentive personal accounting nerd and the fact that they couldn’t produce a conventional income statement or balance sheet was a long running frustration of mine.

    If I had to choose another platform again, I would go with spreadsheets since it can be as simple or complex as you want to make it. I know that’s not really what youre looking for. Wish I had a better suggestion.












  • This shows how short the collective public memory is. There are still people alive today who had polio. I knew an elderly gentlemen who’s face was half paralyzed from having it as a child. Vaccines have increased lifespans and improved the quality of life for humans around the world. Advancements which are now in jeopardy because people lack critical thinking skills and are highly susceptible to bullshit propaganda.



  • There are a few things you can do that will help make everyone’s life easier.

    First thing, ask engineering what can be done to reduce technical debt and then fight for it aggressively. This is often a hard sell to the product owners at first because it can increase the time it takes to produce new features, at least initially. In the long term, it will pay huge dividends to everyone involved.

    When tech debt gets ignored on a new project, the timeline usually goes something like this:

    • Project is barreling toward MVP at lightening speed. The Product owner said “move fast, break things” and engineering is delivering based on that mindset and everything seems to be going great.

    • MVP is almost ready but uh oh! Now a new feature has been requested.

    • “Move fast, break things” doesn’t allow time for code that is easily understandable or extendable to fit new use case scenarios so a huge chunk of the codebase has to be rewritten to accommodate the new feature.

    • Wash, rinse, repeat.

    Without a major change in design philosophy, the cycle tends to get worse over time with small features requiring more and more extensive refactoring and the number of regression bugs skyrocketing. Not to mention the code base is now a disorganized, smoldering pile of spaghetti that every dev loathes having to work on. Stakeholders are unhappy. Customers are unhappy. Engineers are unhappy. Everyone is unhappy.

    Second thing, talk to some actual users, people who are NOT involved in the project, to get their feedback. As an engineer, I like working on projects that add value to someone’s life, or at least make their work day easier. I want the user experience to be positive. I want the features I’m working on to enhance that experience. I don’t want to waste my time working on features that are completely useless and will be rejected by the users as such just because some VP who doesn’t understand what the users want has a bright idea. I’ve experienced this a lot throughout my career and to some degree it’s curbed my interest in software engineering, simply because I feel like a lot of my time and effort were wasted on projects or features that were DOA.