Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
cjfd
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
16 ms
·
271.
▲
by
cjfd
3y ago
I am sure that people who design roads worry about distracting drivers with too many signs. In any case, when one sees five road signs in twenty meters of road, one is lucky if one of them registers. It is very unfortunate when similar worr
272.
▲
by
cjfd
3y ago
This is not so very 'of course'. There is lots of documentation nazis out there forcing you to document that get_height 'gets the height'.
273.
▲
by
cjfd
3y ago
I think this is completely false. It completely breaks down as soon as you get into your first refactoring that is a bit larger than completely trivial. Typically the mess one ends up is one or more of the following. (1) Nothing is refactor
274.
▲
by
cjfd
3y ago
Sure, if you have a few enums with each a few possible values, by all means do this. However, as soon as you get to have, let us say, some more enums that each have a hundred values or so, not only need to serialize them but also need to de
275.
▲
by
cjfd
3y ago
I have seen many comments that are the opposite of wisdom.
276.
▲
by
cjfd
3y ago
Well, one can also get through a book by reading a quarter of an hour a day.
277.
▲
by
cjfd
3y ago
You need both. The type system is not going to catch if you do Rectangle(width, height) where you should have done Rectangle(height, width).
278.
▲
by
cjfd
3y ago
I think it should be pretty obvious that for instance retry logic should be near the place in the code where the first attempt is made. The best case for gathering all errors in a 'railway' is when they can be handled uniformly. E
279.
▲
by
cjfd
3y ago
5 days is very quick. I have an open pull request that has been open for 6 months or thereabouts.... :-( No, I am not suggesting this as a good practice.... Actually, I would say that a pull request should be reviewed in 24 hours. Pull requ
280.
▲
by
cjfd
3y ago
Yes, pretty much agree with this word for word. It is very, very difficult to refactor a python application in any sort of reliable way. The standard way of error handling in python appears to be to present the user with a stack trace. Very
281.
▲
by
cjfd
3y ago
It is an interesting question. If there really is nothing besides the same sets of fields repeated three times one could have some metadata that is used to generate what is necessary in all three layers. But... very often something special
282.
▲
by
cjfd
3y ago
What are 'MIS people'?
283.
▲
by
cjfd
3y ago
It becomes a bit less viable during these times of higher interest rates.
284.
▲
by
cjfd
3y ago
Have you ever actually seen a bunch of cars tightly parked on a ferry? If not, google 'cars on a ferry' and click some images. Now, imagine a car somewhere in the middle of the bunch catching fire. Are you going to volunteer '
285.
▲
by
cjfd
3y ago
Yes, I also find 2 spaces for indentation to be completely unreadable. I am not sure it has anything to do with age.
286.
▲
by
cjfd
3y ago
Not sure about the apps. I just use GTD on paper using a paper agenda combined with a binder to store everything. The main benefit is not having to remember everything that has to be done. When I was younger I found it very unpleasant to ha
287.
▲
by
cjfd
3y ago
Or just don't use spaces in filenames. It just causes trouble for no benefit.
288.
▲
by
cjfd
3y ago
Are there many people like that? In actuality, writing software that is some quality is so hard that one needs all help one can get. One absolutely needs type checking and is just not professional without. One absolutely needs automated tes
289.
▲
by
cjfd
3y ago
Actually, in China I saw a map where the cut was in the Atlantic Ocean. I am not sure how wide spread that is but I would say it makes sense for any world map used in Eastern Asia.
290.
▲
by
cjfd
3y ago
I don't have experience with this in Rust but have come to passionately hate this kind of documentation in other language. I think all of pydoc, javadoc and, doxygen are all garbage. If one could apply them sensibly it would not be so
291.
▲
by
cjfd
3y ago
First, make sure you understand the problem. Look at some particular examples of your problem where the solution is clear, understand the components of the problem. When your have a more or less complete image of the problem in your head, m
292.
▲
by
cjfd
3y ago
The truthfulness of this comment depends very heavily on four words: 'for a large project'. This is the problem with the microservices hype. It is so very easy to ignore this four word restriction and start applying them everywher
293.
▲
by
cjfd
4y ago
Well, John Carmack is a game programmer, at least originally. In games one has strong upper limits on how long it can take to calculate the next frame. So, it may very well be that something can be said for this in this context. I am not su
294.
▲
by
cjfd
4y ago
This is the reason I think that for any of those ToS if it turns out that any provision in them is unenforceable it should be that the whole ToS automatically becomes unenforceable.
295.
▲
by
cjfd
4y ago
100% accuracy will never be achievable. What might be achievable, though, is a higher degree of confidence than we currently have. Of course, the correctness of algorithms should also have to have a computer validated proof.
296.
▲
by
cjfd
4y ago
It is not validation if you do it at parse time. Then you can pass a Prime around the whole time and never do the is_prime check again.
297.
▲
by
cjfd
4y ago
class Prime { public: Prime(int p): p(p) { if (!is_prime(p)) throw std::runtime_error("Number was not a prime!"); } int get_value() const { return p; } private
298.
▲
by
cjfd
4y ago
The article makes this very point a few times.
299.
▲
by
cjfd
4y ago
Errors are not inevitable if these calculation are automized. And I would be very surprised if they are not.
300.
▲
by
cjfd
4y ago
This interpretation of renormalization supposes that there is a more fundamental theory at a higher energy scale from which the quantum field theories arise. These then have an effective field theory which is evolved to the energies that ar
More ›