Comments ⌘ Read more
Comments ⌘ Read more
Hey folks, I don’t normally write about more CS-y kinds of things, but I wanted to in this post. I’m pretty sure I did an okay job of representing these ideas to a broader audience, but given that I only got a BS in CS, I may have done less than an okay job. Feedback very welcome.
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Sup friends. I am curious about patterns for modeling data of various types where you just straight up do not persist null values, ever. All fields NOT NULL constrained. But in a way that disambiguates unasked and unanswered questions. Where invalid states can’t be represented, like “none of the above” being stored alongside one of the above. And where there is minimal dependency on app layer logic, db triggers, or complex constraints.
Examples that come t ... ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Every few weeks, a thread on the front page gets dominated by meta discussion about how the author is breaking the self-promo guideline. I propose discouraging this by stating in the guidelines that such comments are off-topic.
If people want to help enforce the guideline, I think it would be better to kindly PM the author the first time, and flag as spam if you think they are knowingly disregarding it.
When it’s a public comment, it often overwhelm ... ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
The ILP problem is given by matrix 𝐀 ∈ ℝᵐ×ⁿ and vectors 𝐛 ∈ ℝᵐ and
𝐜 ∈ ℝⁿ. The goal is to find a vector 𝐱 ∈ ℤⁿ such that 𝐀 · x ≤ b and cᵀ · x is the maximum.
Usually, the problem is given as max {cᵀ · x : 𝐀 · x ≤ b, x ∈ ℤⁿ}.
“A large number of practical optimization problems can be modeled
and solved using Integer Linear Programming - ILP.”
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
This paper introduces a new data-structural object that we call the tiny pointer. In many applications,
traditional log n-bit pointers can be replaced with o(log n)-bit tiny pointers at the cost of only a constantfactor time overhead. We develop a comprehensive theory of tiny pointers, and give optimal constructions
for both fixed-size tiny pointers (i.e., settings in which all of the tiny pointers must be the same size)
and variable-size tiny pointers (i.e., settings in which the average tiny-pointer size must be small, ... ⌘ Read more
Comments ⌘ Read more
Rhombus is ready for early adopters.
Learn more and get it now at https://rhombus-lang.org/
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
This story was originally a comment in reply to another post. I mention primarily LLMs, but the same criticisms apply to image generation, especially w.r.t. data collection (stealing).
* * *
> LLM crawlers continue to DDOS SourceHut posted/shared by fratti
This s ... ⌘ Read more*
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
What are you doing this week? Feel free to share!
Keep in mind it’s OK to do nothing at all, too. ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
I’ve volunteered to teach my colleagues about git - at least one of whom seems to know nothing of it.
Obviously, I don’t want to start from scratch. Which tutorials have helped you, or helped you get people up to speed?
We’re using gitlab, I don’t need to cover true distributed workflows, just forge-oriented git usage to collaborate with colleagues. ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Using a web archive link because the original blog’s stylesheet seems to recently have broken
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Linking to reddit feels strange (and I had to condense the title-summary), but the project documented it in this post and I believe this is worthwhile to look at. The comments amass a lot of interesting stuff namely: similar attacks using [this](h ... ⌘ [Read more](https://www.reddit.com/r/golang/comments/1jbzuot/someone_copied_our_github_project_made_it_look/)
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more
Comments ⌘ Read more