douglasg14b

@douglasg14b@programming.dev

• ⁨Comment⁩ on ⁨How do you manage code snippets?⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  I go full chaos and look up where I last used it when I need a snippet…

• ⁨Comment⁩ on ⁨I'm a hypochondriac, but It's About Programming⁩ ⁨⁨7⁩ ⁨months⁩ ago⁩:

  Someone who shares their experiences gained from writing real world software, with introspection into the dynamics & struggles involved?

  Your age (or mostly career progression, which is correlated) may actually be a reason you have no interest in this.

• ⁨Comment⁩ on ⁨I've lately been making my git commit messages with AI⁩ ⁨⁨7⁩ ⁨months⁩ ago⁩:

  And what does it imply?

  That an AI might be better at writing documentation than the average dev, who are largely inept at writing good documentation?

  This sort of post is just bad faith, doesn’t actually make any conclusions, and is just a disguised way to shit on others as opposed to contributing to the discussion at hand.

• ⁨Comment⁩ on ⁨What is your favorite software stack for full-stack web development?⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:

  Yessss.

  C#/.Net backends are the best. The long term stability, DevX, and the “it just works” nature of all the tooling makes it a great choice. It’s also fast, which makes scaling for most applications a non-issue.

  I’ve switched to postgres for DB from SQL server, have never looked back, would recommend.

• ⁨Comment⁩ on ⁨What is your favorite software stack for full-stack web development?⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:

  .Net + Vue + Postgres.

  I can get applications built extremely quickly, and their maintenance costs are incredibly low. The backends are stable, and can hang around for 5, 10+ years without issue or problems with ecosystem churn.

  You can build a library of patterns and reusable code that you can bring to new projects to get them off the ground even faster.

  Would recommend.

• ⁨Comment⁩ on ⁨Hours of work⁩ ⁨⁨10⁩ ⁨months⁩ ago⁩:

  If you do this enough you know how to design your solutions to be relatively flexible. At least for your backends.

  Your frontend will always churn, that’s the nature of the job.

• ⁨Comment⁩ on ⁨The Case for Developer Experience⁩ ⁨⁨10⁩ ⁨months⁩ ago⁩:

  I think you can have a well tended garden without giving up creativity.

  You’re not sacrificing creativity by practicing structures, considerations, and methodologies that maintain or improve the developer experience with whatever creative endeavor you’re on.

  The structure of your garden doesn’t prevent you from playing around with new plants, it just outlines a set of patterns and expectations known to drive better outcomes.

  I’m not saying that your extension of the analogy is bad I’m just disagreeing with some of the premise.

• ⁨Comment⁩ on ⁨Inside the Workflow Metrics of Elite Dev Teams⁩ ⁨⁨10⁩ ⁨months⁩ ago⁩:

  Pretty much.

  For instance focusing on PR size. PR size may be a side effect of the maturity of the product, the type of work being performed, the complexity or lack thereof of the real world space their problems touch, and in the methodologies habits and practices of the team.

  Just looking at PR size or really any other single dimensional KPI lead you to lose the nuance that was driving the productivity in the first place.

  Honestly in my experience high productivity comes from a high level of unity in how the team thinks, approaches problems, and how diligent they are about their decisions. And isn’t necessarily something that’s strictly learned, it can be about getting the right people together.