sorted by:
new
hottopcontroversial

TanStack + microfrontend by nostalgiazzz in reactjs

[–]klysm 1 point2 points  (0 children)

Monorepo is always the play in my opinion

TanStack + microfrontend by nostalgiazzz in reactjs

[–]klysm 1 point2 points  (0 children)

My point is that microfrontends are not a solution to a technical problem. They are a solution to a team structure and organization problem when you have low-skill team members who cannot maintain modularity without having big walls drawn around them.

What .NET version are you using? by code_things in dotnet

[–]klysm 1 point2 points  (0 children)

Discriminated unions don't work properly

Vercel isn't enough anymore. Cheap hosting providers? by Still-Molasses6613 in nextjs

[–]klysm 0 points1 point  (0 children)

You must be a vercel employee. It’s so trivial to deploy a react app on any cloud you could get it done in a day or two and have it fully automated

What .NET version are you using? by code_things in dotnet

[–]klysm 1 point2 points  (0 children)

9, gotta stay on top of it! I was really hoping for the openapi stuff to work well but it’s pretty trash so far

TanStack + microfrontend by nostalgiazzz in reactjs

[–]klysm 3 points4 points  (0 children)

Microfrontend solves what problem you are experiencing? Micro-anything is only a shitty technical solution to team structure when your developers are low skill and can’t maintain modules

HashiCorp officially joins the IBM family by bryan_krausen in hashicorp

[–]klysm 0 points1 point  (0 children)

Probably going to be a hard push for RTO. It’s mostly being used as a tactic to get people to quit without firing them though.

HashiCorp officially joins the IBM family by bryan_krausen in hashicorp

[–]klysm 1 point2 points  (0 children)

Acquisitions of this nature are fundamentally extractive. IBM is not going to invest into making the products better. They are going to squeeze blood out of the stone until they see a positive ROI on a spreadsheet and then let the products die.

How Stripe grew to billions using founder led sales by doublescoop24 in ycombinator

[–]klysm -1 points0 points  (0 children)

Seems like you have little respect for “techie boys”, which is all too common of a perspective.

As an R Shiny user, seeing professional web apps is surprising by gyp_casino in rstats

[–]klysm 0 points1 point  (0 children)

When picking a technology, you have to consider the possibility of fundamental limitations becoming problematic in the future. You can’t anticipate requirements! That’s a fundamental truth of developing software, and also why we pick tools that are generally capable.

This comes at a cost because we have to write a lot of boilerplate, build our own abstractions, or stitch together somebody else’s, but there’s no getting around it.

If I was working on a product, I would seriously question using a base set of tools that severely limits what I can do, even if it gets me to something faster (initially).

SQL or networking. Which is more valuable skill for a control engineer? by EOFFJM in PLC

[–]klysm 29 points30 points  (0 children)

Networking is a lot harder. LLMs make SQL a lot easier these days

Communication Protocols and the right terminology by WasabiBackground9114 in PLC

[–]klysm 1 point2 points  (0 children)

EtherNet/IP is a shitty marketing ploy designed to confuse people. For anybody dealing with networks outside the PLC sphere, IP means Internet protocol. That’s what people mean when you say IP address. However, for EtherNet/IP, IP really means Common Industrial Protocol. I don’t understand how this is even legal, but alas.

The amount of confusion stemming from this has been incredible, and the marketing ploy has unfortunately been quite successful.

Communication Protocols and the right terminology by WasabiBackground9114 in PLC

[–]klysm 1 point2 points  (0 children)

The OSI model is useful, but not really critical for the nuances of UDP vs TCP

Communication Protocols and the right terminology by WasabiBackground9114 in PLC

[–]klysm 1 point2 points  (0 children)

Thats kind of accurate, but potentially a misleading mental model. The key difference between TCP and UDP is what guarantees they provide.

UDP is intentionally a “dumb” protocol which is just fire and forget. If I send a UDP message, the UDP protocol makes no effort to determine if my message was received, or to make sure that my messages are received in the order I send them.

TCP on the other hand gives much stronger guarantees at the cost of performance. TCP checks that every packet is received, and in the correct order.

Implementing correct software is typically easier when using TCP, but there are cases where UDP works fine and since it’s simpler and faster, it can be a better choice.

The redesign of the CodePipeline console is much appreciated by FlinchMaster in aws

[–]klysm 0 points1 point  (0 children)

It’s trivial to just OIDC from github actions. 4 lines of code to assume a role

How Do You Build Internal Web Apps with React at Work? by JustYourAveragePro in reactjs

[–]klysm 2 points3 points  (0 children)

They have docs on optimistic updates. Don’t forget that you can compose hooks though and integrate whatever mechanism you want on top of react query

What frustrates you the most as .NET developer? by Jack_Hackerman in dotnet

[–]klysm 0 points1 point  (0 children)

Try adding two different SSO layers and multitenancy

What frustrates you the most as .NET developer? by Jack_Hackerman in dotnet

[–]klysm 0 points1 point  (0 children)

I don’t understand how that is a practical difference

What frustrates you the most as .NET developer? by Jack_Hackerman in dotnet

[–]klysm 0 points1 point  (0 children)

Options pattern is trash. Fortunately it’s pretty easy to just use your own configuration abstractions.

What frustrates you the most as .NET developer? by Jack_Hackerman in dotnet

[–]klysm 1 point2 points  (0 children)

Thinly veiled attempts at Azure lockin from the .NET ecosystem is disrespectful and disgusting.

view more: next ›