HackerTrans
トップ新着トレンドコメント過去質問紹介求人

aleksiy123

820 カルマ登録 5 年前

コメント

aleksiy123
·6 日前·議論
I don’t think that’s really true.

Both exist. I would say single player games tend to content in the range of 10+ hours. Think First Light, Ghost of Yotei in recent years.

Competitive and multiplayer games will tend more towards what you are thinking. CSGO, FIFA, and of course many others.

But I feel like even that doesn’t really capture the full range of everything.
aleksiy123
·11 日前·議論
Manual type? No cron job?

Practically Luddite
aleksiy123
·18 日前·議論
Is it just me or is this really not that crazy of an idea?

Polls are already a thing, and people love giving their opinion on things.

Combining social media and gambling while maybe not morally great. Seems like has potential to make a shitton of cash.

Betting is all over the place right now.
aleksiy123
·22 日前·議論
Wasn’t this case pretty much before?

The limits are 100 workers on free and 500 on paid.

And if need more then you can always go their platform which supports tenancy.

As long as you have a cronjob or similar to clean up the cost of having per PR preview is pretty much zero.
aleksiy123
·23 日前·議論
fighting the urge to rewrite everything and propagating the legacy code cycle.
aleksiy123
·26 日前·議論
Finally just bought a piece of my own hardware and got LLM to deploy k3s cluster on it.

I think diy homelab/hosting is more accessible than ever.

Cut costs on cloud spend and invest into AI spend.

For a solo dev on a budget, I think it just makes sense.
aleksiy123
·27 日前·議論
Not in the Clausewitz definitions I think.

Strategy would be the use software to achieve business goals.

Essentially why are we doing this at all.
aleksiy123
·28 日前·議論
If writing code is tactics and the end goal is strategy.

Is architecture operations?
aleksiy123
·29 日前·議論
Somewhere within c++ there is a subset of c++ that is a great language.

The problem of course is that no one agrees on which subset that is.
aleksiy123
·先月·議論
I pretty much always prefer using an options struct as soon as there is more than one optional argument.

Comes out cleaner because overriding a default argument doesn’t force you to also do all the positional arguments in front of it.

Designated initializers make it look really nice imo. I feel like the brackets are no big deal.

Python has sort of the opposite when you need to use *kwargs.
aleksiy123
·先月·議論
Interesting, I do think blending the fuzziness of models with the determinism of hard checks/conformance is the way too go.

But using some kind of metrics as guardrails/steering seems interesting.
aleksiy123
·先月·議論
Severance really captured that vibe.
aleksiy123
·先月·議論
It’s not even obvious that it isn’t conscious imho.
aleksiy123
·先月·議論
Or even have Claude actually go through the whole process of thinking about story structure, iterating on it, reviewing, editing, researching etc.

I feel like people expect Claude to just 1 shot a good story from their 2 sentence prompt.

But even a human needs to sit down and apply a structured or semi structured process over a non trivial amount of time/turns/iterations.

If you asked most people to write a short story out of nowhere with no context and 1hr. Most of them are gonna write some generic stuff.
aleksiy123
·先月·議論
Isn’t the fact that you just referenced it indicate that they do?

I feel like it’s probably just complexity.

Different workloads benefit from specific types of optimisations.
aleksiy123
·2 か月前·議論
I think for big groups it’s not so much luck/randomness that is the key but complexity. Low complexity games are going to play better. They can be pure skill games. Many drinking games are (beer pong etc).

Luck/randomness is directly against determinism. A way of making feel less mechanical and opening up the combinatorial state space? Essentially increasing the fun/interest without introducing high complexity necessarily? As well as narrow the skill range as you say, but not necessarily over longer time horizons.

Like you can do a 2d matrix of luck and complexity.

Tic tac toe - low randomness, low complexity

Chess - low randomness, high complexity

Poker - med randomness, high complexity

Roulette - high randomness, low complexity
aleksiy123
·2 か月前·議論
I saw someone in a different thread describe Google product/tool strategy as a: “monkey knife fight”

And tbh I can’t really argue with that.
aleksiy123
·2 か月前·議論
how effective is RTK for you? worth using?
aleksiy123
·2 か月前·議論
Its arguing that that source code that affects the behaviour of something should be easily discoverable from the point/points its behaviour affects. or alternatively more indirection/obfuscation is worse.

Its not so much about same file, as reducing distance to understanding, whether visually or by some sort of easily traceable path.

Like you would want to init a variable closer to its usage, Or that having a 100 wrapper functions is less understandable than inlining for a single statement, or global mutations are harder to trace then local, and that sometimes its easier to inline a single sql statement then split it out into a different file just because its 2 different languages.

Also, to be clear its possible to write CSS that exhibits less or more LoB. The file thing is more that I don't think HTML, CSS, JS "must" be written as separate files which is what the prevailing best practice used to be, justified as SoC. I just think splitting along the scope/behaviour lines rather than file type is more understandable.
aleksiy123
·2 か月前·議論
End users and even other programs/extensions can load rules to alter your styles. I think thats about as opposite of locality of behaviour as it gets. (no judgment on customization on being good/bad).

With the rest I don't really strongly disagree. I think its just a question of complexity. For simple things its fine, but for complex apps with teams of people :shrug: