douglasg14b

joined 2 years ago
[–] douglasg14b@programming.dev 8 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

The number of new devs who complain about having to write a unit test is too damn high

  • Or writing integration tests
  • Or passing CI
  • Or following repo conventions
  • Or following standards
  • Or adhering to domain guardrails
  • Or in adding monitoring
  • Or in not logging everything as info
  • Or in actually documenting features
  • Or in receiving critical PR review
  • Or in addition input validation
  • Or in not trusting the client

...etc

Honestly most devs.... Kinda suck at their job. This is becoming more evident to me every year

[–] douglasg14b@programming.dev 16 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

I work remote (Going on 9 years now) and I miss a sense of community. Do I want to stop working remotely? Hell no, screw that. But two things can be true the same time, I can enjoy and encourage them at work, dnd I can also miss a sense of community.

I think it's okay to hold this opinion because it's individual to everyone.

This just comes across as propaganda

Being dismissive and pulling the rhetoric that this is propaganda is toxic as fuck.

[–] douglasg14b@programming.dev 2 points 2 months ago

Hospital near me has password requirements for their electronic medical records system as:

  • 6 characters, no more, no less
  • 2 characters must be a number
  • 4 characters must be a letter
  • case insensitive
  • never changed

And for new hires and what not, they tell them to use {hospital abbreviation}{2 digit year}. Like casu24

No freaking wonder

[–] douglasg14b@programming.dev 1 points 3 months ago* (last edited 3 months ago)

Why would it be on each dev to setup?

Your repo can, and should, include workspace settings for major editors that provide a uniform experience for anyone onboarded to the platform.

I agree that precommit hooks are good for uniformity. But slow pre commit hooks are frustrating, they are also often turned off. Your CI will always be the last gatekeeper for linting/formatting rules regardless.

Making precommit hooks slower means more devs disable them, which is the opposite of what you want. Save them for simple, read, checks and validations that can run in < 1s for even huge changesets.

[–] douglasg14b@programming.dev 2 points 3 months ago

Is that even legal?

I mean if you own a real estate, it doesn't cost more just because the plot of land becomes popular. You can sell it for more, sure.

I don't get how your registrar can suddenly boot you out from under a domain just because someone else is interested in it that has money.

Shouldn't that person or company have to offer you money to buy that domain?

[–] douglasg14b@programming.dev 1 points 3 months ago* (last edited 3 months ago) (2 children)

Or on save even. Slow pre commit hooks suckkkk

[–] douglasg14b@programming.dev 1 points 3 months ago* (last edited 3 months ago)

That's not a linting problem that's a formatting problem.

That project should have automatic formatting on save setup.

Linters are not necessarily formatters they're solving two different problems and are becoming increasingly separated in their toolset.

[–] douglasg14b@programming.dev 4 points 11 months ago* (last edited 11 months ago)

Too bad commenters are as bad as reading articles as LLMs are at handling complex scenarios. And are equally as confident with their comments.

This is a pretty level headed, calculated, approach DARPA is taking (as expected from DARPA).

[–] douglasg14b@programming.dev 1 points 11 months ago* (last edited 11 months ago)

Doesn't appear to show any charts on Chrome for mobile...

Seems to be a responsiveness issue, because it goes away in landscape mode, and the charts show.

[–] douglasg14b@programming.dev 6 points 11 months ago* (last edited 11 months ago)

They work great when you have many teams working alongside each other within the same product.

It helps immensely with having consistent quality, structure, shared code, review practices, CI/CD....etc

The downside is that you essentially need an entire platform engineering team just to set up and maintain the monorepo, tooling, custom scripts, custom workflows....etc that support all the additional needs a monorepo and it's users have. Something that would never be a problem on a single repository like the list of pull requests maybe something that needs custom processes and workflows for in a monorepo due to the volume of changes.

(Ofc small mono repos don't require you to have a full team doing maintenance and platform engineering. But often you'll still find yourself dedicating an entire FTE worth of time towards it)

It's similar to microservices in that monorepo is a solution to scaling an organizational problem, not a solution to scaling a technology problem. It will create new problems that you have to solve that you would not have had to solve before. And that solution requires additional work to be effective and ergonomic. If those ergonomic and consistency issues aren't being solved then it will just devolve over time into a mess.

[–] douglasg14b@programming.dev 13 points 11 months ago (1 children)

Because your conservative funded news outlets have a very overt goal here.

[–] douglasg14b@programming.dev 40 points 11 months ago

The CEO is a right wing trump worshiper.

Dig into the company's tweet history, and find archived tweets that were deleted for PR/white-washing reasons.

Long history of this stuff.

 

I'm looking for some sort of chores calendar where we can set up scheduled chores each day and assign an owner to them.

If those chores are not done then they start to stack onto the next day.

My spouse and I need to hold each other accountable for the chores and tasks in which we are assigned. And I think a great way to represent that is showing how uncompleted chores stack up, they don't go away, the time it takes to complete them still exists as a form of debt to our free time.

Are there any open source projects that do this sort of thing or help with keeping up with the home, tasks, & household chores?

 

GitHub: https://github.com/microsoft/garnet

Just saw this today and I am pretty stoked. It's just a drop in replacement and performs > 10x faster under workloads with many client connections. Not that I found redis slow, but in Enterprise workloads that's a lot of money saved. $50k Garnet clusters handling similar workloads for $5k would be significant.

It being essentially entirely written in C# makes it pretty easy to read, understand, contribe to, and extend. Custom functions in C# have a pretty low barrier to entry.

I get that there's probably going to be a lot of hate just because this is released by Microsoft developers.... But in my opinion the C# ecosystem is one of the best to build on.

view more: next ›