I use it when I need to deeply understand a PR.
1,423 karma · joined December 2, 2015
Paratrooper to programmer.
http://github.com/jschaf
hn@schafer.dev
I use it when I need to deeply understand a PR.
This is the essence of how to make the medical system work for you. Advocate for yourself. AI helps know what to ask, why you should ask, and how to get past the first few layers of dismissals.
The fee agreement was an hourly rate for producing a legal document. The resulting document looks like it took 10 seconds to produce. The lawyer billed $1000 worth of hours.
So, either the document was much more complex than anticipated (in which case the lawyer should have said so), or the lawyer inflated the hours.
So, if a lawyer bills $1000 for "10 seconds of work", it smells fraudulent.
If $1000 was a flat rate, then it's similar to software: you're purchasing some IP and passing off legal liability to the lawyer. How long the lawyer spent on it doesn't matter.
Go shipped with generics (aka bounded parametric polymorphism), but only for built-in types: slices, arrays, and maps. That, with subtyping via interfaces, handled most demand for generics. The most common pain point was custom containers.
Go was first released in November 2009. Russ Cox posted "The Generic Dilemma" [1] in December 2009. The comments show the generics debate raging from the earliest days.
As a fun side note, I forgot I posted a comment on that post pointing to Ada's generics. I was in college, and Ada was our intro language.
[1]: https://research.swtch.com/generic
> the designers didn't want that complexity inside Go.
Yes, with some nuance. Go's goal of writing server programs didn't require the type-system complexity and run-time hit of user-defined generics. [2]
> Go was intended as a language for writing server programs [...] Polymorphic programming did not seem essential [...] so was initially left out for simplicity. > > Generics are convenient but they come at a cost in complexity in the type system and run-time. It took a while to develop a design that we believe gives value proportionate to the complexity.
[2]: https://go.dev/doc/faq#beginning_generics
Out of curiosity, I collected all proposals for Go's journey to generics. https://gist.github.com/jschaf/eaa7aff1af14ea7276a18a1b7370d...
“He weathered the storm” vs “the stone weathered into an arch”.
I'd wait for more details before adjudicating.
I had the same issue when looking to adopt ConnectRPC for Go, which uses a custom wrapper type to model requests.
[1]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
Tinder provided 1-mile granularity, so OPFOR would roam around until they had enough points to locate the headquarters. Then, they'd artillery it out of existence. The brigade commander was most displeased—moving a brigade headquarters is not for the weak or fainthearted.
I’m not sure about cargo audit specifically, but most other security advisories are package scoped and will warn if your code transitively references the package, regardless of which symbols your code uses.
Pre-commit checks should be opt-in with CI as the gate. It's useful to be able to commit code in a failing state.
Here’s a good issue describing the tradeoffs between a lock table and advisory locks.
0-18 months: 1:3
18 months to 3 years: 1:4
3-5 years: 1:5
Anecdotally, I lost 26 lbs in Ranger School.
One problem with using a channel as a semaphore is you need to track if you've closed the channel when "releasing".
https://pkg.go.dev/golang.org/x/sync/semaphore#Weighted.Acqu...
PE has access to business models unavailable to the original owner.
- Buy all local dentist clinics at an enticing markup then increase rates.
- Buy businesses and migrate them to tech where the PE firm holds an advantage. For example, a PE firm that runs its own payment gateway.
- Buy a business that complements a larger business to reduce churn or increase sales.
> The goroutines run in parallel. Also, don't use complicated words when simple words will do.
That’s not called for, especially since you’re wrong.