Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
leghifla
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
by
leghifla
5y ago
In your post: "There's no more time-honored way to get things working again, from toasters to global-scale distributed systems, than turning them off and on again" This is generally true, but as all rules, there are exception
32.
▲
by
leghifla
5y ago
When I was still a student, I accidentally erased all my project source code with: rm * .o I was puzzled by the message ".o: No such file", and then understood why... Now, I always start with ls and if satisfied of the output, rep
33.
▲
by
leghifla
5y ago
From reading the article, I think the author of the post has ego issues: "we are actually seeking satisfaction from the looks of envy and admiration that we draw from others" Admiration maybe from someone close to me, but envy? I
34.
▲
by
leghifla
5y ago
About prioritizing, I want to share a story: We were a small and good team developping hardware/software combos. We ruined a demo to a client by promising some hard to do feature, and during the demo, the said feature had not been well
35.
▲
by
leghifla
5y ago
Or, say, your Samsung washing machine detects on your home network your Bosh fridge and try to use any vulnerability to brick it (and the fridge tries to brick the washing machine too). Appliance war... If people know this, it would be a in
36.
▲
by
leghifla
6y ago
I don't know about management, but the guys on the factory floor were aware and happy with it. It made their job more convenient too, and the supplier was marketing its solutions as secure, so don't worry ;-)
37.
▲
by
leghifla
6y ago
Well, put too much inconvenience and some "smart" guy will circumvent it anyway. I have not personnaly worked in industrial environment, but from people I know, security wise, it is very scary at some places. Here is one such exam
38.
▲
by
leghifla
6y ago
"they don't have a good idea of who's benefiting and who's losing" This reminds me of a poker analogy: if you sit at a table and do not recognize the idiot at the table, it's you
39.
▲
by
leghifla
6y ago
I am the first to ask for quick feedback loops, which makes the dev environment so much enjoyable. But I have also seen some detrimental long term effect of this. I have seen developpers "coding to the test". By that I mean they a
40.
▲
by
leghifla
6y ago
"Teach your employees that if you don’t want to be interrupted you better write good documentation." And reward them for doing it. If your company do "360 degree" evaluations where your peers praise you for your quick an
41.
▲
by
leghifla
6y ago
It is never too late, but do not let that be an excuse to delay any decision. 42 here, already two major career changes. And I am glad I made both changes.
42.
▲
by
leghifla
6y ago
Sorry I do not understand your weight/force analogy. I assume that in a car, both sides have equal weight/inertia. Anyway, I did write "approximately" to avoid discussing acceleration/inertia of the differential its
43.
▲
by
leghifla
6y ago
The differential (ignoring locking ones) applies the same force (approximately) to both wheels. If you remember your physics course about lever and force, see the video at 5:00, you can see that the lever is pushed by its center, hence both
44.
▲
by
leghifla
6y ago
I did that for Richard Burns Rally
45.
▲
by
leghifla
6y ago
Usually, the more competition there is in a market segment, the lesser the margin becomes. Let's say your customer often "complement" your offer A with B from another company. If the other company faces fierce competition on
46.
▲
by
leghifla
6y ago
> If you’re a strong writer and you can consume information in written formats really well Most comments here are focused on the "write well" part, which is important, no doubt. But let's not forget the "read well&quo
47.
▲
by
leghifla
6y ago
You need incentives for the maintainer helping others to learn. AND you also need incentives for the others to start learning. I am living right now this situation where I am the maintainer of a large chunk of code, I would like to have at
48.
▲
by
leghifla
6y ago
It seems really interesting at first glance, but having worked with high-speed cameras, filming a mosquito at 30m at 2000fps will only be practical in a bright sunny day. Some clouds or at night and you will need kW's of light just for
49.
▲
by
leghifla
6y ago
When Schumacher moved to Ferrari, Ferrari was not at all the best car, far from it. But the relentless work he did there improved the car far faster than the other team could. HE made the car better. It was an era with no (or few?) limitati
50.
▲
by
leghifla
6y ago
"Master/slave is debatable, because it isn't actually discriminatory" As a white man, I cannot tell if some black people are offended by that, but I hope not. I had never thought about racism when discussing technical ma
51.
▲
by
leghifla
6y ago
There is no encapsulation like in OOP (data level), but there is another kind of encapsulation (process level): a process is the only one accessing/modifying its own state. And this is very liberating when you need to think about what
52.
▲
by
leghifla
6y ago
I once "solved" a tricky issue with a random bug in an FPGA processing data from DDR. The issue was hardware "malfunction": DDR can flip some bits if accessed in some ways. No one on the team did know about that, no one
53.
▲
by
leghifla
6y ago
You think you are safe, until a TV crew broadcast your post-it worldwide. It is not made up, it happened to TV5Monde in 2015
54.
▲
by
leghifla
6y ago
I think the human error was made possible because of AI: the AI can search millions of records. The police / detective cannot and will only search a very small set, limiting the search by other means. The probability of finding an inno
55.
▲
by
leghifla
6y ago
Well, I would not want to get into the car of someone with a driving habit of risking the live of 1000 people in the first place. The real solution to this is to avoid situations where such choice must be made, by keeping safe distances and
56.
▲
by
leghifla
6y ago
Also sometimes, long lines can more easily render the structure of the program. Like when a function is called with many/long arguments several times in a row, with varying arguments. If you have one line per call, you can easily see t
57.
▲
by
leghifla
6y ago
Do you know if your neck strain is due to horizontal or vertical movements? On a few times I had to work with big monitors (>30"), I noticed that I placed/sized windows only at the center, and not all the way to the top. Lookin
58.
▲
by
leghifla
6y ago
On the other hand, I used this behaviour to my advantage in the DOS era. I had written a small utility to easily start my games (a Pascal program). My goal was to get as much memory free for the games. To allow unloading my program before l
59.
▲
by
leghifla
6y ago
1 Ws is just 1 J (1W = 1J/s). Just for comparison with a more widely used unit, you need 3.6 million J to make one kWh.
60.
▲
by
leghifla
7y ago
"can describe ... pros/cons of their approach" I've always tried to do that... until recently. With a new recruit, this is the fastest way to nightmare discussions. He always emphasizes the cons of my proposals, and neve
More ›