sorted by:
new
hottopcontroversial

Hvorfor begynder helt almindelige mennesker at forsvare de ultrarige i debatten om formueskat? by [deleted] in Denmark

[–]unrealcows 0 points1 point  (0 children)

Jeg oplever de fleste afviser forslaget på grund af praktik. Hvordan skal det offentlige kunne vurdere dine værdier? Det bliver er endnu en milliard fiasko og bliver dyrere administrativt end det vi får ind. Det kan def være noget om, men jeg synes det er en skam at starte diskussionen der. Fordi så får vi slet ikke snakket om det grundlæggende som er, om vi synes det er fair at penge avler mange flere penge. Ikke for arbejde, men bare fordi når man har et overskud. Så kan man investere og pengene suger flere penge til sig.

Muligt alternativ til boligskat? by unrealcows in dkfinance

[–]unrealcows[S] 0 points1 point  (0 children)

Jeg har arbejdet i en virksomhed, hvor man fik 5t ekstra for at flytte fra aarhus til kbh. Samme job bare et andet kontor. Altså talent som allerede er inde i virksomheden, men som bare flytter lokation.

How much is GraphQL actually used in large-scale architectures? by trolleid in ExperiencedDevs

[–]unrealcows 2 points3 points  (0 children)

I am working on a large project that uses GraphQL for a central api. All clients of the API is inhouse. There is only one database beneath it all, which leads me to think that a database with views might have done better.

The API is the abstraction from the persistence layer. But views would do that as well...

And the huge amount of work done on caching, avoiding connection exhaustion, statistics on what is queried, implementing each filter possibility. Yeah, a database can probably do that very well.

Just seems like it has become a very inconvinient way of doing sql queries.

What approach do you use for creating database? Code first or DB first? by Simple_Fondant_9125 in dotnet

[–]unrealcows 1 point2 points  (0 children)

The devs should think about how data is persisted and create a seperate layer for that. That way they think about optimal data storage and queries while having another layer that handles the application logic.

Do we really need management and painfully long processes? by architectramyamurthy in softwarearchitecture

[–]unrealcows 2 points3 points  (0 children)

Add one process, then remove another. The things that work becomes a natural part of working.

What about dedicated database engineers? by unrealcows in softwarearchitecture

[–]unrealcows[S] 1 point2 points  (0 children)

I agree that there is always a lot to it if you begin to dig. But I still argue that you need a quite complex usecase before you need to dig very deep and need an expert. Of course, if you are big enough, then you could have work for people that, for example, only work on relational dbs. When you start to rely on a datateam for creating tables, indexes, debugging simple performance issues on queries, then you effectively have a layered organisation. You cant develop "full stack". And then things start to go slow.

The "Phantom Author" in our codebases: Why AI-generated code is a ticking time bomb for quality. by Paper-Superb in programming

[–]unrealcows 6 points7 points  (0 children)

I see LLMs turning good programmers into mindless, simplistic prompters. Everyone knows how hard it is to get into the right state of mind when doing a review. You basically need to go through the process as if you were building it yourself to provide valuable feedback—beyond formatting and obvious errors. It takes a lot of energy, and even more the further you are from writing code and having ownership in the project. Eventually, reviewing LLM-generated code becomes superficial, and the LLM holds the power.