karmakaze
Multiple features?
> Maybe we just didn’t do a good enough job. Maybe the code was just not good enough. We’ll learn and improve. It’s probably some of that, and I’m mentioning it here to not give the impression that it was only the other factors that I’m going to mention.
> It could also be a coincidence. Maybe we had been on such a good roll that we attempted to tackle several features that turned out to be too hard, or at least too hard to finish in time.
All of the above seem clearly the case--not that it could be realized at the time of cutoff and not getting it cleaned up in the window.
> we, meaning all the developers affected, have had enough time to fully reflect on all this.
Title should be: The reverts will continue until quality improves. Humour is good for the clicks but also a means of deflection. I sort of feel bad saying without putting in effort contributing myself but having it merged would have been worse.
The proprietary models 'cheat' on this since they generate but don't send output thinking tokens to be counted. So to grade them we have to use cost or time.
[0] https://artificialanalysis.ai/?intelligence-efficiency=outpu...
The search providers I pay likely don't pay their sources. Some others (that I don't use) don't even have the original text only providing summaries. Some offer both.
> He first pursued corporate science jobs and prestigious postdoctoral fellowships at national laboratories. Then he cast a wider net, applying to software engineering and other roles. Eventually, he was getting ghosted for food-preparation jobs, including at a company that sells frozen crab cakes.
> For a time, Weis got a gig training AI on his expertise, including in engineering and fluid mechanics. That work dried up too.
I surmised that they expected a certain kind of job. Couldn't get it, then applied to general 'software engineering' jobs and was out-qualified by other applicants. Did some basic jobs and decided that wasn't their cup of tea. Note you can also be overqualified for basic jobs. I worked part of a summer in retail at a sports/clothing store training with high school kids. I was directly asked why I was applying and I answered that I was bored and had a lot of spare time. Ended up outlasting many other hires through the summer and quit in the winter. Best position ended up being in womenswear--I gave frank looks great/better/worse answers which seemed to be highly appreciated.
Their 8-bit stuff were the best hardware designs. Anything that would have surpassed it went with Jay Miner and the Amiga.
Where Atari really failed was not creating the next gen from the stockpile of money from VCS/2600--waited for the market to crash only to have NES produce the next wave using 6502+Audio Ricoh chip. Their 5200/7800 consoles were too late and expensive.
Almost all my programming foundations were learned hacking on the 8-bit Atari computer. Great times.
> Overall, I’m pretty excited for this. It’s not like I need yet another Atari 8-bit computer since I already have an 800, 800XL, 130XE and (non-working) 1200XL. But those are all 40+ years old at this point and can be fragile.
I have the Atari 400 Mini but I wouldn't mind adding THE 800XL to my collection. I grew up on the original membrane keyboard 400, had an 800 and 1200XL, and collected a 130XE.
The search providers I pay likely don't pay their sources. Some others (that I don't use) don't even have the original text only providing summaries. Some offer both.
Two signals I use: do I ever push back and find places where the draft version was incorrect, incomplete, or otherwise not up to par and do I feel comfortable if something goes wrong with in production and I have to debug it at any hour of day or week.
Verdict for “https://openfatigue.ai/”:
Formerly Open
Openness score: 9%
Was open until it got popular
License changed on a Friday at 5pm
Community forked it and called it OpenFormerly
Is this a joke site? First Pricing card Open
$0/mo*
Read the README
Star the repo (required)
Join the Discord (read-only)
~~Run the software~~ [strikeout]
[Get Open]And the Apple Max/Ultra does it better. The Mac Mini/Studio form factor makes way more sense. These laptops look like conspicuous consumption brand marketing devices. CUDA is worthless--AIs can port kernels.
Only when we get to M5 Max 614 GB/s and Ultra 1.2TB/s does it get interesting for me.
whoami
uname -a; cat /etc/issue
date
pwd; curl http://ipv4.icanhazip.com
df -h; free -h; # htop[0] https://serpbase.dev/blog/serpbase-vs-serper-dev-serp-api-pr...
I'm not nearly as particular with my OS backups as I used to be. For instance Desktop personalization is minimal. I've used too many computers over the years to maintain much configuration beyond a small number of dot-files. Hobby code goes in Github/codeberg.org and some kind of cloud sync for my daily driver.
Another thing that ended up happening naturally is that I keep hard drives of old computers when I upgrade. They serve as point-in-time snapshots. I haven't made it a point to be able to necessarily read all of them but it doesn't take much like having a number of USB-disk/media interface adapters around.
The best I could figure is that I like to start with requirements, use AI to discuss and settle on its high level design and specific aspects of its implementation. I may or may not read all the code, but the key thing is even if I didn't read the code in advance, doing so would not be a surprise and I'd know what it was doing and how it was doing it because those were things I decided during the up-front conversations and not left as an open exercise for the AI. And coming back to the codeberg.org vote I can guess that it was elements like these that they wanted to guard. They don't want repos whose owners don't know what the code does in a technical sense or how it's constructed etc. There's likely other things too like seeing text that doesn't read like people wrote it and I find that tiring to read (in a literal way, I get drained from reading too much of it) and endorse minimizing that.
Another thought was that my ever long search for better and better programming languages was that if I have a clear vision of what I want the language should have the least friction to write it down. Some languages that feel closer than others were Elm, Elixir, F#/OCaml, Pony, Rust, Kotlin, Go. Only a couple of these are my languages I'd regularly used but would prefer to have my AIs write in them. For web I'd probably also accept Vue, Svelte, or (simple) React. In particular using Go for mini back-ends is particularly effective as the coding style tends to be regular and boring which minimizes differences between human and machine written styles. So in a sense giving specs at multiple levels of abstraction and detail is the perfect high level language I'd been wanting.
> The communication must be made in a manner in which another person may view it.
Even 'transmitted' is too broad if you also consider iCloud backup to be a means.