Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
chipdart
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
29 ms
·
391.
▲
Fake Biden Robocalls Cost Wireless Provider $1M in FCC Penalties
(gizmodo.com)
1 points
by
chipdart
2y ago
|
1 comments
392.
▲
by
chipdart
2y ago
> I suppose you are technically correct that noexcept can throw to themselves. But that's just being pedantic, isn't it? No. There are comments in this thread from people who are surprised that you can still handle exceptions w
393.
▲
by
chipdart
2y ago
> If you were reading the documentation for function foo() and it read "if the argument is negative, foo() throws an exception" (...) I think you didn't understood what I said. In C++ functions declared as noexcept are exp
394.
▲
by
chipdart
2y ago
> How is related to sociopaths though? Are you really asking what sociopaths have to do with setting up their team member for failure by intentionally steering them into a wrong path so that they could throw them under the bus? > Also
395.
▲
by
chipdart
2y ago
> What if I really disagree with the design and the way we're going about the project and think it will fail. You just need to grow a spine and express your concerns. Alternatively, if growing a spine is not an option, you forego an
396.
▲
by
chipdart
2y ago
> what.. noexcept throws exception..? what kind of infinite wisdom led to this Not wisdom at all, just a very basic and predictable failsafe. If a function that is declared to not throw any exception happens to throw one, the runtime han
397.
▲
by
chipdart
2y ago
> (...) throwing an exception in a noexcept function is undefined behavior. Small but critical correction: noexcept functions can throw exceptions. What they cannot do is allow exceptions to bubble up to function invokers. This means th
398.
▲
by
chipdart
2y ago
> I’ve certainly had off days reviewing someone’s work and only realised certain feedback later. It's one thing to get back to the review and say "hey I just noticed something I didn't noticed earlier, and I feel it's
399.
▲
by
chipdart
2y ago
> Do you mind sharing a concrete example? If you're interested on the topic, you can start by reading up on "disagree and commit". To weed out sociopaths, Amazon even went to the extent of coining their leadership principl
400.
▲
by
chipdart
2y ago
> I actually don’t have a problem with this because just because it looked good conceptually, doesn’t me it is going to look good before going live. That's perfectly fine. That's also not the case, though. The case in question
401.
▲
by
chipdart
2y ago
> I think this situation would've happened regardless of advice vs permission. I don't think so. If you have a process in place where everyone can and should be heard during the design process and once the design is approved it
402.
▲
by
chipdart
2y ago
> I have seen these behaviors only when I work with toxic engineers. I think it is pretty clear that the need to have all team members commit to projects after the design review is to prevent backstabbers to stab other team members in th
403.
▲
by
chipdart
2y ago
> Be careful not to burn bridges so quickly. I don't think your comment makes sense. You're talking about a scenario where, when you ask someone to review your design, their feedback is literally "all good, looks fine to m
404.
▲
by
chipdart
2y ago
> …and when someone asks for your permission (probably because you’re in the person’s management chain), one response could be: “you don’t need my permission, if you think it is a good idea after getting input, go for it. If it turns out
405.
▲
by
chipdart
2y ago
From the article: > (...) but if it goes wrong you might end up involving them in the failure: “Hey, I asked that team and they said it was fine.” I've seen this play out in teams. The part that's omitted is how some unscrupulo
406.
▲
by
chipdart
2y ago
> If this is all in native Rust then you could do something interesting with macro defined SQL queries, where at compile time, you could output direct bindings from the SQL to the internal DB api. Aren't table references resolved at
407.
▲
by
chipdart
2y ago
> There is a choice between very few phone manufacturers, and even less mobile operating systems. I don't think that the manufacturer assertion is true at all. You can go to any random online store and get dozens of brands and manu
408.
▲
by
chipdart
2y ago
> "buy it or don't" does not work with oligopolies. If you had a free market, I would agree, but you very much don't in this case. Why do you believe there is no free market on mobile phones? I mean, what exactly forc
409.
▲
by
chipdart
2y ago
> While true and a fair point, iOS is Apple’s platform in a way that the web is most certainly not Google’s. OP was whining over Google's role in Android. Pointing out Apple's control of iOS, and the fact that iPhone is by far
410.
▲
by
chipdart
2y ago
> Things may get worse for a while, but then maybe they'll eventually get better than (...) This argument is perplexing. Isn't the whole point of this sort of intervention to fix things that are broken so that everyone is bette
411.
▲
by
chipdart
2y ago
> If your of the opinion that Google should not be broken up at all, ever, then your point is valid. I don't think it's a good sign that you decided to resort to baseless personal accusations in reaction to a simple request to
412.
▲
by
chipdart
2y ago
> artificially suppressed rates I don't follow your point. All rates are set arbitrarily according to the monetary policy followed on any specific moment. What leads you to believe that arbitrarily setting a rate one way is natural,
413.
▲
by
chipdart
2y ago
> If what comes after is not better, then we waited too long to break this monopoly up. I don't follow your logic, because it does not have any logic. Can you clarify your line of reasoning? I mean, if breaking up a company creates
414.
▲
by
chipdart
2y ago
> do you have specific examples of what lead you to this conclusion? Just get a spec, run kiota,and check the output. Compare with the output from, say, openapi generator. No one can miss the difference.
415.
▲
by
chipdart
2y ago
> (...) but as "describing how performance changes as the size of the input data increases". Yes, that's the definition of asymptotic computational complexity. That's the whole point of these comparisons. It's po
416.
▲
by
chipdart
2y ago
I think that smartphones with full keyboard and auto complete/autocorrect get you faster than 10wpm. Even the old number pad phones would beat that in the hands of your average 90s teenager.
417.
▲
by
chipdart
2y ago
I've ran a few tests with Kiota and I found that the generated code is awkward and needlessly hard to integrate. It's good to have options available but with openapi-generator around I hardly see the point of bothering with Kiota.
418.
▲
by
chipdart
2y ago
A TDP of 170 Watt is quite the beast. I don't think that it's reasonable to claim this isn't a major concern just because it's a desktop processor. This reflects in operational cost and anything directly and indirectly r
419.
▲
by
chipdart
2y ago
> It does not necessarily describe performance of the algorithm. Not necessarily true. It does indeed describe performance of the algorithm. It just compares scenarios with coarser granularity. You can tell from the very start that a O(1
420.
▲
by
chipdart
2y ago
> No, they don't. They are police officers, not lawyers. How do you enforce laws that you don't know or understand? Think about it. These guys mobilize themselves to use force to achieve their goal. How is step 0 of this whole
More ›