euske · HackerTrans

Looks like that the project has changed its name from "rmc" (Rust Model Checker) to this. Various sources point to rmc as https://github.com/model-checking/rmc (redirected to https://github.com/model-checking/kani) and https://model-checking.github.io/rmc/ (404). Anyone knows why?

euske

5년 전discuss

I actually think that defining the metrics is half of the game for productivity. Once you define the metrics, it's relatively easy to game it.

That said, I think software development is a relatively well defined task. There's typically some clear need from clients, and there's some restriction. Your problem space is somewhat confined.

Now, corollary is this: the more restriction you have, the easier you can be productive (or invent a way to be productive). Specialists can be generally more productive than generalists because they can have a more precise definition of "being productive".

euske

5년 전discuss

Actually this is kinda standard in Japanese ryokans. Many places offer umbrella/rain boots for rent, and hotel staffs marking pathways on their giveaway map is common. Now, it's possible that they might have went an extra mile for a clueless (as they thought) foreigner, but I find this kind of thing a little too nosy. This probably explains why many Japanese people prefer a more businesslike Western hotel today, and ryokans are more or less for foreign tourists.

euske

6년 전discuss

It's like asking how to become a cook. There's just so much variety to it - it could be hobby, professional, corporate, or artisanal, etc. You can't give any more specific answer to that.

euske

6년 전discuss

I think this is a common strategy of big players at any industry.

First, they do some dirty thing to gain a competitive edge when the industry is still new and unregulated. Later they develop an alternative way to achieve the same competitive edge, and then criticize other players for doing an old way, saying they should be "mature and responsible".

euske

7년 전discuss

I think that we could add some random (i.e. pure luck) factor for evaluation. Although this may sound unfair, almost all optimization problems do this, be it natural or man-made. Evolution does this by adding random gene mutation, and machine learning does this by randomizing certain parameters to avoid being stuck at local minima. In theory, the right mixture of rigid metrics and randomization can make a better result.

euske

7년 전discuss

I think this is more of an adult's problem. The transition from kids to teens and adults is awkward everywhere, but it's particularly bad in Japan, as they're pretty much coerced and funneled into the workaholic (and misogynistic) society. But when kids are being kids, they're fine.

euske

7년 전discuss

I think it's a time that we should get rid of this notion of "perfectly safe code in the perfect world". It might be possible if the code doesn't change for million years, but that's not how the world works - things keep changing, the specs, the requirements and the users. Bugs are created every day. It's not about safety as a static property, but it is about the safety in an ever-changing world. As Bruce Schneier put it, it's a process. And yes, C++ might be bad for it, but that's only a part of the whole picture. We should look at the process rather then the code itself.

euske

10년 전discuss

"In a capitalist economy, the market rewards things that are rare and valuable. Social media use is decidedly not rare or valuable. "

This sounds such a short-sighted argument. Do people greet others because they expect some sort of rewards? It's a basic courtesy. Yes, some people overdo it but using a social media moderately could be a good norm. Again, the balance is the key, and we'll still need a bit more time to figure out the right amount of dose for each, but rejecting them outright is equally misguided.

euske

11년 전discuss

I highly recommend "The Psychology of Computer Programming" by Weinberg to this list. One of the best books about programming that I've ever read.

comments