Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Sankozi
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
19 ms
·
211.
▲
by
Sankozi
4y ago
Each one of them: 1. is a person that solves logical puzzles if possible 2. knows that the other one + (insert point 1 here). 3. knows that the other one + (2) 4. knows that the other one + (3) ...
212.
▲
by
Sankozi
5y ago
No it is not. It assumes you store money gained under the bed and do not reinvest it in any way.
213.
▲
by
Sankozi
5y ago
To any single integration test to be precise. So your builds fails few seconds later if something is wrong.
214.
▲
by
Sankozi
5y ago
If we divide whole map into small enough regions then all of them would be "green" by your reasoning. All kinds of problems can be "solved" that way.
215.
▲
by
Sankozi
5y ago
I recently thought about the same thing. The problem with rental system is user now has less incentive to treat rented item well. But overall I think it still leads to less production and less resource usage.
216.
▲
by
Sankozi
5y ago
I disagree. You are basically saying that only end to end tests are very good tests. There are different reasons to have tests. Unit tests often break even during small refactorings but are great to quickly cover of lot of edge cases of som
217.
▲
by
Sankozi
5y ago
> With cash, the moment the object and the bills change hands, the funds transfer has irrecovably settled without any external dependency being possible. It isn't even remotely true. You might get mugged, you might lose money, you m
218.
▲
by
Sankozi
5y ago
"you have to work a little" It can easily be benefit for example if you work 1/8 time for 1/2 of pay.
219.
▲
by
Sankozi
5y ago
Paying humans to do things that machine does better and safer definitely does not have better utility.
220.
▲
by
Sankozi
5y ago
I disagree that corruption is rare in USA. You could say USA "solved" corruption problem by legalizing it. If you agree that legal action cannot be corrupt then you probably could say that corruption is rare in the USA, but I doub
221.
▲
by
Sankozi
5y ago
In SQL NULL does not mean "no value" it means "unknown value". Existence of such value introduces three value logic because expression "NULL = <anything>" is neither true nor false. This makes queries har
222.
▲
by
Sankozi
5y ago
5% return per year (or more in case of price changes or regulations forcing you to change heating source) does not seem that "philosophical".
223.
▲
by
Sankozi
5y ago
"SELECT whatever FROM thisplace" is trivial to improve and could be for example thisplace[whatever]. With joins it gets more complex but still SQL could allow using foreign keys and having SELECT at the end. You could get at least
224.
▲
by
Sankozi
5y ago
It is more like starting the recipe with "take sauce from point 6 and pour it over meat from point 10". Very few people has problem with trivial queries like "SELECT x FROM y", but when query contains multiple joins or i
225.
▲
by
Sankozi
5y ago
There is a stigma with having "head problems". I think it is more useful to fight with that stigma than to ignore existence of problems like depression or psychosomatic disorders.
226.
▲
by
Sankozi
5y ago
I think I do not understand the numbers. You wrote "costs/duration" so higher the number the worse solution (bigger costs or worse durability), yet the descriptions suggests otherwise.
227.
▲
by
Sankozi
5y ago
> Nah. One of the most common uses of null is to communicate missing values in the sense of "this entity has this attribute but we don't know what its value is". This is a fundamental feature needed in data management. I r
228.
▲
by
Sankozi
5y ago
Snappiness problems are often due to lazy loading Java classes. For example first time loading project settings takes 1+ seconds while next less than 0.5. This value might get lower later if JVM decides to optimize more some parts of UI app
229.
▲
by
Sankozi
5y ago
I did not meant the same CO2, just any available fossil fuels. I find it would be great if we could convert CO2 to something that cannot be profitably burned.
230.
▲
by
Sankozi
5y ago
If you had process that only needs electricity then you run it only when power is cheap (usually when renewables are producing it). Depending on efficiency this could be better solution than energy storage (instead storing energy you pull C
231.
▲
by
Sankozi
5y ago
>> full teams can and have built huge java projects just by using the intellij project wizard and maybe a tiny bit of Gradle from stack overflow. > They are the kind of programmers who have a very narrow range of abilities, and whe
232.
▲
by
Sankozi
5y ago
Market forces are not fully understood in complex systems but it does not mean they do not work. Forcing employers to give more money to employees (rising wages through regulation) may cause some unexpected/unaccounted things (more con
233.
▲
by
Sankozi
5y ago
I have never had to decide which exact Maven version (Java build tool) to use in team and on CI server when developing in Java. Most of the times you can safely use any version of Java that is higher than currently required in project. My t
234.
▲
by
Sankozi
5y ago
The problem is undefined is used in places null makes much more sense (like a result of the find function). I follow the rule to never use null and convert to/from undefined if needed by some library.
235.
▲
by
Sankozi
10y ago
Unfortunately newThing = {...thing, propertyName: value} Will always compile, even if propertyName is invalid. The only advantage over Object.assign I see is IDE support (at least in Intellij IDEA). I will still use: newThing = O