• 0 Posts
  • 26 Comments
Joined 2 years ago
cake
Cake day: July 26th, 2023

help-circle




  • I’ve gone through Visual Studio, JetBrains IDEs, Vim, Atom, Sublime, VSCode, probably others too, but frankly VSCode’s simplicity out of the box coupled with great plugin support is hard to beat. Folks who complain about VSCode not having some feature like to ignore that being relatively simple by default is a good thing. You can always add or enable what extensions you need to tailor it to your language and workflow of choice. Even if you’re used to Vim keyboard centric editing…guess what? There’s a well supported OSS extension to give you that functionality.

    The power of being able to use one IDE on a diverse team across various languages is huge. You can even commit extension and settings defaults to a repo to immediately get new cloners up to speed with whatever workflow and tooling defaults are good starting points on a per project basis, but still leaving them the option to ignore/override as needed without dictating a team-wide workflow change.








  • It’s actually that a small cheap home and a large expensive home aren’t much different in cost for a builder, but the second nets way more profit. So no builder wants to build and sell starter homes. Thus, housing shortage for working class people looking for affordable homes.

    Somewhat still impactful is that construction has a worker shortage, but that’s probably in part cause they don’t get paid enough to attract more new tradespeople. If they DID get paid enough, it would drive up prices further since builders still want the same cut and their margins aren’t that crazy to begin with.

    How do we incentivize building and selling starter homes? They need to be more profitable relative to expensive big homes, or working class people need more income to afford them to increase demand at rates builders would make good money on due to volume.

    I think the growth of townhomes for sale and five over one condos is helping with this somewhat, but not enough. Many of those get used for apartments or short term rental too because those are still more profitable than just selling.


  • Yeah management is totally backwards there; it’s like the building manager on a construction project going “all electrical needs to be done in X weeks”, but realistically they have no direct control over that deadline being met by declaring an arbitrary deadline. The unfortunate difference is that if you do a shitty job wiring a building, you’ll fail inspection and have to spend more time and money fixing it. Software can often hobble along; there aren’t strict enforcements for quality that the business can legally ignore, so you’ll always have sad defeated devs go “okay boss, we’ll skip the things we need to get this done faster for you (I hate this job and don’t care about the product’s long term success)”. Having a steady supply of those people will slowly kill a software company.

    In the past, I’ve dealt with estimate pushback not by explaining what necessary work can be removed like tests, documentation, or refactoring, but by talking through ways to divide the project more effectively to get more people involved (up to a point, a la mythical man month). That seems to go more proactively. Then we look at nixing optional requirements. But, I’ve also usually dealt with mostly competent engineering management.


  • The thing that frustrates me about developers who feel powerless over technical debt is…who is actually stopping them from dealing with it? They way I see it, as a software engineer, your customer is sales/marketing/product/etc. They don’t care about the details or maintenance, they just want the thing. And that’s okay. But you have to include the cost of managing technical debt into the line items the customer wants. That is, estimate based on doing the right things, not taking shortcuts. Your customer isn’t reading your commits. If they were, they wouldn’t need you.

    It would be bizarre if your quote for getting your house siding redone included line items for changing the oil on the work truck, organizing the shop, or training new crew members. But those costs of business are already factored into what you pay at the end of the day.




  • I really wish we could focus on the actual causes of high government spending instead of this or that tax rate.

    I tend to think it’s due to use it or lose it budgets. Same thing happens outside government too. You get a chunk of money to use, and if you don’t spend it all, you’ll probably get less next year. If you spend it all, you might be able to argue for more next year since you ran out.

    There’s little incentive for the groups doing the spending to save a lot of money, especially if they know they only take a tiny piece of the enormous pie. But it collectively causes that pie to have to be enormous.

    Is there any real world solution to this endemic behavioral incentives problem with some history of large scale long-term success? Naive solutions can easily backfire or lead to corruption. You don’t want to incentivize cutting so much that necessary spending is impacted either.