HN user

ivxvm

44 karma
Posts0
Comments45
View on HN
No posts found.
Dopamine Fracking 1 month ago

Yeah, when people say "dopamine hit" nowadays that can mean anything from serotonin to endorphins to even adrenaline. What they usually mean is simply an optimized experience. Optimized, commodified, industrialized, etc, in a way article describes.

Recommendation to research something still can be useful. I didn't word it right. It should have been something like: "Add it to your list and research it if you're out of options". It helped me with some weird condition years ago which could have been depression but it had zero symptoms other than severe chronic fatigue, so maybe it wasn't.

Necropolis, Ziggurat... Imo the best games nowadays are often those that no one heard about. Popularity wasn't a good metric for a very long while. And thankfully games like "New World" and "Starfield" are helping a lot for general population to finally figure this out.

It's interesting thing to explore when you already have a nice big picture, but overall it's quite misleading in case of genres (or whole branches) which author is not much into.

I think you get the wrong idea. What he basically says is that scientists mostly do science because they enjoy doing it, and everything else he says is a consequence of that. People in general tend to gravitate to activities which they enjoy in terms of process, and science is no exception. Usefulness of their work would be a nice side effect, but people rarely do things purely for result, especially when it's something that requires a lot of time and efforts. Basically we are inherently hedonistic creatures and there's no way changing that.

I'll just save some quotes here since I really like them:

Kaczynski likened science to a “surrogate activity” that is “directed toward an artificial goal that people set up for themselves merely in order to have some goal to work toward” or some sense of fulfillment.

“Scientists work mainly for the fulfillment they get out of the work itself,” he wrote. “… Thus science marches on blindly, without regard to the real welfare of the human race or to any other standard, obedient only to the psychological needs of the scientists and of the government officials and corporation executives who provide the funds for research.”

Idk, I think it's extremely statistically rare coincidence for nominative typing to be a better default than structural. In other words, it's much more useful (by default) to have some function work on more types than be a little bit more type-safe for the exactly the type author had in mind when writing it. In my opinion, type-safety has diminishing returns and the most of its usefulness lies in trivial things, like passing a string instead of some object or array just as a typo, or writing a wrong field name when mapping one object to another, but nominative typing lies way beyond my imaginary line marking the zone when types become more of annoyance than help.

Not really possible, because Record and Map aren't compatible at all. At best they both have something like `toString`. You'll need to define at least something like RecordFunctor<T> and MapFunctor<T> to make this useful.

Javascript is dynamic enough there is absolutely no need for Macros.

TypeScript macroses would be very useful for the same things codegenerators are useful: for example generating api client from swagger schema. Ofc you can do some trickery with metaprogramming, for example build and eval strings on fly and the result could be a dynamically generated function, but the point is: we want the process and the result to be typesafe and efficient, which is what is missing with hacky dynamic metaprogramming approaches.

But presumably there is also more competition for jobs using popular technologies?

Maybe, but personally I don't feel it has such a significant contribution as number of positions you can apply to. In these languages you basically can find a dozen of positions worldwide open at any given moment of time and apply to them, in JS you can find hundreds upon hundreds of positions every day and just filter and keep applying, and it still can take weeks or months to get an offer, a lot of your applications aren't even processed at that moment, which could be the case with less popular tech positions as well.

Another reason is that being a fan of less popular tech is heavily punishing to career and job hunting. Hell, it's quite a challenge to find a job even in React/JavaScript (took me a good month or even a bit more last time, and I'm a senior dev), and it would be a nightmare for languages/ecosystems like Haskell or Rust. I wouldn't even want to find another JS job because I don't want to go through a month of such struggle again, and if I were a Haskell dev I would be afraid to lose that job like I will die if I do. Nowadays, I don't even want to touch stuff like that simply because it would be unhealthy for me to become interested in tech that makes my life so much harder and stressful. I would probably think about it only if companies started sending me positions with better-than-senior-React rates themselves proposing to pay me for learning their required stack on the go.

I think the whole concept of "consciousness" might get old in nearby future. ANNs and brains will get better understood and people start questioning not what consciousness and reasoning are, but rather why they feel their "now" as they do, whether they are full of energy and in sharp mental state or they drunk to half death and can't really reason and form sentences normally yet still perceiving their "now" in the same way and feeling like they are still them. I don't know if there is a better word for this concept, but it definitely feels like the word "consciousness" shifts away from this meaning each day.

has made all of its progress by throwing chairs (data) at the problem.

To me it seems like the most tricky thing about the whole field is that quantitative adjustments make qualitative breakthroughs. Simply increasing parameters / layers / data make sudden rapid jumps in generalization / abstraction / etc. It's somewhat unintuitive because many things in world don't work like this, and the metaphor you're discussing is more about "normal" things, it doesn't really apply to ANNs well, those are more of anomaly, like quantum mechanics (yeah, it's probably a bad analogy too).

Product owner is the one who analyses requirements, decides what should be implemented, and creates user stories for programmers. Currently programmers can use AI to help implement user stories but in future probably AI will be good enough take and implement user stories on its own. In more distant future it could replace product owner too. So that CEO can just talk AI directly into making a great product without much details, but at that point businesses like this will be less valuable because many can do that and there's no need for devteam and less need for investments.

I wouldn't be surprised if John Carmack combines activities of product owner, game designer, and programmer. In most industry cases, programming jobs are not like this. There are dedicated positions for people who focus on delivered value and it's not programmers. So in scrum terms, he might actually be saying that programmers will be indeed obsolete, but product owners, game designers and other kinds of business analysts not.

What a nice idea it was to scroll immediately and figure out this is another bullshit reactive programming evangelism blogpost. Bro, we've already had this shit in JS like 20 years ago (Flapjax anyone?). Now go on and write your code like this for at least few weeks and see how great and maintainable and "fine-grained" it becomes.