Readit News>Coleman died homeless and destitute in 2006. It was unlikely he was aware of the impact he had made on music. Neither he [band leader Spencer] nor Coleman received royalties for the break.
[1] https://en.wikipedia.org/wiki/Rainbows_End_(Vinge_novel)
> I don’t like using code that I haven’t written and understood myself.
Why stop with code? Why not refine beach sand to grow your own silicon crystal to make your own processor wafers?
Division of labor is unavoidable. An individual human being cannot accomplish all that much.
> If you’re not writing in binary, you don’t get to complain about an extra layer of abstraction making you uncomfortable.
This already demonstrates a common misconception in the field. The physical computer is incidental to computer science and software engineering per se. It is an important incidental tool, but conceptually, it is incidental. Binary is not some "base reality" for computation, nor do physical computers even realize binary in any objective sense. Abstractions are not over something "lower level" and "more real". They are the language of the domain, and we may simulate them using other languages. In this case, physical computer architectures provide assembly languages as languages in which we may simulate our abstractions.
Heck, even physical hardware like "processors" are abstractions; objectively, you cannot really say that a particular physical unit is objectively a processor. The physical unit simulates a processor model, its operations correspond to an abstract model, but it is not identical with the model.
> My control freakery is not typical. It’s also not a very commercial or pragmatic attitude.
No kidding. It's irrational. It's one thing to wish to implement some range of technology yourself to get a better understanding of the governing principles, but it's another thing to suffer from a weird compulsion to want to implement everything yourself in practice...which he obviously isn't doing.
> Abstractions often really do speed up production, but you pay the price in maintenance later on.
What? I don't know what this means. Good abstractions allow us to better maintain code. Maintaining something that hasn't been structured into appropriate abstractions is a nightmare.
> What? I don't know what this means. Good abstractions allow us to better maintain code. Maintaining something that hasn't been structured into appropriate abstractions is a nightmare.
100% agree with this. Name it well, maintain it in one place ... profit.
It's the not abstracting up front that can catch you: The countless times I have been asked to add feature x, but that it is a one-off/PoC. Which sometimes even means it might not get the full TDD/IoC/feature flag treatment (which aren't always available depending upon the client's stack).
Then, months later get asked to created an entire application or feature set on top of that. Abstracting that one-off up into a method/function/class tags and bags it: it is now named and better documented. Can be visible in IDE, called from anywhere and looped over if need be.
There is obviously a limit to where the abstraction juice isn't worth the squeeze, but otherwise, it just adds superpowers as time goes on.
https://www.bleepingcomputer.com/news/security/fake-one-batt...
To be fair, jQuery was a response to the the IE and JS variant mess of the early 2000s. jQuery made development possible without debugging across three browser varients.
Yes means yes, no means no, "how was your weekend" and then down to business. It's a pleasure interacting with them.
Funny story, the lead on our Eastern European team told me a while back that he had to tell his team:
When the North Americans ask at the beginning of a meeting "How's it going?", they do NOT really want to know how you are doing. It's just social lubrication before getting to work.
Before that, we were getting to learn that their mother in-laws in town or different medical issues.
Still waiting for the ecosystem to mature a little more and the "early" movers to consolidate the APIs. Also, I love my job so not super motivated.
The only business "secret sauces" I know are creativity (market value depends on what you're selling) and implementation (if what you're selling works). Customers will follow.
IMO: Go For It! The more the space matures, the better for all of us.
https://en.wikipedia.org/wiki/Rainbows_End_(Vinge_novel)#Aug...
Isn't this the point of the whole conversation we are having here?
Laws on copyright were not created for current AI usage on open source project replication.
They need to change, because if they are perfectly enforced by the letter, they result in actions that are clearly against the intent of the law itself.
The underlying problem is that the world changes too fast for the laws so be fair immediately