Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
strictfp
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
18 ms
·
181.
▲
by
strictfp
6y ago
Maybe we should think about the consequences of making retention the number one KPI?
182.
▲
by
strictfp
6y ago
Rust is tricky. Took me about a year to grok decently. Regarding references, the compiler does flow analysis and tries to enforce a sort of static rwlock semantic on variable level. You either have a single mutable reference xor N readable
183.
▲
by
strictfp
6y ago
Take what he writes with a grain of salt. Highly productive people like himself likely gets free rein, and so they're looking at the process with rose-tinted glasses. I've worked with some of these process gurus, and sadly most of
184.
▲
by
strictfp
6y ago
Same here. Could it be some rate limiting of the height data? I'm on a Samsung S20.
185.
▲
by
strictfp
6y ago
It would be great. We need a way of preventing "death by a thousand cuts" by bloated organizations and processes. I also think it would be good to upturn most processes since people learn how to exploit systems quite quickly. But
186.
▲
by
strictfp
6y ago
Well, the novelty of course. Everything has it's way. Radio, TV, telephony, the internet; all have gone through different phases of commercialization and exploitations. It takes time for bureaucracy to take over. Think of the natural c
187.
▲
by
strictfp
6y ago
https://en.m.wikipedia.org/wiki/Fortitude_(TV_series)
188.
▲
by
strictfp
6y ago
i.e an ABA problem
189.
▲
by
strictfp
6y ago
In a sense, all security is by obscurity. Security-wise, your PIN is in fact pretty much equivalent to a random port.
190.
▲
by
strictfp
6y ago
I share the opinion that DoD is an optimization technique, and that it shouldn't be applied too generously from the get-go; you're essentially optimizing for specific usage patterns, which might be difficult to predict and often a
191.
▲
by
strictfp
6y ago
Not so sure about that. I know plenty offices in Stockholm with free food, drinks and entertainment for employees.
192.
▲
by
strictfp
6y ago
Happened to me as well. Was writing an authentication service. We thought we were paying for an actual security audit, turns out we payed for a simple word scanning of our codebase. The review didn't find any of the canaries we left in
193.
▲
by
strictfp
6y ago
This is what I'm also afraid of.
194.
▲
by
strictfp
6y ago
But then "Gay" just meant happy. And "retard" means slightly slowed down (development). Those were probably all decent words from the start. The words aren't the problem, their usages are. I'm not convinced tha
195.
▲
by
strictfp
6y ago
Incremental development in Rust isn't particularly slow; it's compiling all the dependencies which takes the most time, and when you make changes you only recompile your local crate, which typically is quite fast.
196.
▲
by
strictfp
6y ago
Consider using wrk2 in order to avoid coordinated omission.
197.
▲
by
strictfp
6y ago
Coll simulation! I'm looking for any pointers to noise or other generative methods which looks like eroded terrain from the get-go, without the cost of simulating the erosion process. Any tips appreciated.
198.
▲
by
strictfp
6y ago
Yes! This is spot-on. This is a social construct and a good example why I think we should focus more on male gender roles in order to achieve better equality. Males have strict roles, expectations and reward structures in society, just like
199.
▲
by
strictfp
6y ago
I'm convinced that the best thing we as society can do for gender equality right now is to abandon the corporate roles that cater unreasonably much to the stereotypical macho male gender role. These are roles which in principle require
200.
▲
by
strictfp
6y ago
I always found it ironic that you get most of this for free if you design your sql updates and save/query the transaction log and/or history. A lot of relational dbs have functionality for that. And if you don't want to use t
201.
▲
by
strictfp
6y ago
One other huge downside of frameworks is that they don't (easily) compose with other frameworks and libraries.
202.
▲
by
strictfp
6y ago
I guess most holes got patched. I worked with the same things around 2007.
203.
▲
by
strictfp
6y ago
The thing is that this is too much magic. You end up wasting time getting your literal right. Whereas Cs solution is simple and just works.
204.
▲
by
strictfp
6y ago
I much prefer Cs solution to this problem; you can write multiple literals in sequence and they will be concatenated: char* text = "hello" " dear" " sir"; This is great, because it doesn't make le
205.
▲
by
strictfp
6y ago
I'm not convinced. It would use every trick in the book to punch holes; stun, upnp, sip, it's own protocol on top of udp, it would even send data over port 80 or 443. And if that failed Skype would use a third Skype client to open
206.
▲
by
strictfp
6y ago
Think of all the open source libs. Generally speaking, anyone can contribute to any part of the project. That's not to say that some people are better than others at certain parts of the codebase, but you don't want people fightin
207.
▲
by
strictfp
6y ago
That's generally true, and it's a big problem with microservices, because they need so much upkeep. But if your code is living as a few hundred or thousand readable lines in the common codebase, that isn't really a problem. T
208.
▲
by
strictfp
6y ago
I agree with you in such cases, but I'm willing to bet that most codebases don't need to be as big as they are, and that it's better to create an incentive to collaborate and keep the codebase maintanable and small.
209.
▲
by
strictfp
6y ago
I think the ties arise because people are actively seeking areas of responsibility. Software components are an obvious grab if your eyes are on the software specifically. But there are other ways of dividing your teams; based on for instanc
210.
▲
by
strictfp
6y ago
Noo! Building teams around software components cements your architecture and prevents most cross-cutting improvements. I'll claim that splitting a well-structured monolith into microservices will always make it less maintanable, but it
More ›