What I would like to see for vibe coded novelty apps that are not realistically going to see updates are the prompts-as-source. For instance, I one-shotted a Roku app to play the HackerTube listings, and it works good enough:
Build a sideloadable Roku channel/app for browsing and playing videos from
https://hackertube.org/. Inspect HackerTube's API or video pages and use Roku
BrightScript/SceneGraph. Deliver a complete zipped Roku channel with source,
setup instructions, and any necessary metadata/proxy details. Aim for Roku
Developer Mode sideloading.
Source for one-shotted apps so LLM gives you repo back and template to build on instead of burning electricity on ideations from scratch.
I imagine 90% of stuff could be just that.
But I also imagine people just cloning repo don’t feel it truly belongs to them, but when agent slops out code for them somehow they feel like they did the work themselves.
Agreed! We desperately need an OSS framework of basic modular building blocks for the new generation of vibecoders, if nothing else just to stop the massive waste of resources of having all the models build the same thing hundreds of thousands of times.
SaaS is only dead if you believe you paid only for software there is still part “as service” because running and maintaining software still takes time even if slopping out software is virtually free.
This Saas is no more! It has ceased to be! 'E's expired and gone to meet 'is maker! 'E's a stiff! Bereft of life, 'e rests in peace! If you hadn't nailed 'im to github 'e'd be pushing up the daisies! 'Is CI/CD processes are now 'istory! 'E's off the twig! 'E's kicked the bucket, 'e's shuffled off 'is mortal coil, run down the curtain and joined the bleedin' choir invisible!! THIS IS AN EX-SAAS!!
I'm thinking that if somehow we could force temperature to 0, it could even be "prompt as compressed source". In the sense that you know if you run a given prompt through a given model version you would get the exact same results.
This could have some space applications. You send a powerful model to space, iterate with the same model on earth and once the results are good only send the prompt to the remote model... Well, now that I'm typing it, I guess if the model is good enough you don't even need that and only give it a goal before leaving.
I think it's the future for prompt-based engineering honestly. I employ it myself too. I Keep a prompts file, either for sharing or looking back at it. I think Open Source Software should adopt it in their repos for a. transparency and b. learning material for the future.
I hadn't thought of that, but that's a really good idea - prompts as source code. you're right, most of them will never see a formal update, so the prompt is a great way to hand off some control.
Perhaps it could be restructured to separate out the howto from the explanation to serve the reader’s intended use at the time as described here: https://diataxis.fr
As a tech writer I love the concepts of Diataxis but don't agree with it being invoked here. Context is critical in all four of its quadrants, and its model doesn't apply uniformly to every aspect of every application.
GP did IMO the right thing by understanding the audience first in order to judge what level of context is appropriate. That should be rule 0 before anything in Diataxis gets involved.
I think another factor is the medium through which the docs are to be consumed. If the intended audience are "experienced, technical professionals" as the ggp says, but those folks are arriving at the docs primarily from search engines, then it's likely they are in "how-to mode" [0].
People in "how-to mode" are almost always time-constrained. They need immediate answers so interspersing the why with the how would slow such readers down (since they have to scan more text than they need to [1]). Their impatience will often cause them to bounce from your web page back to the search engine in search of other sources that can provide them with immediate answers.
Without additional context on the medium of delivery of the docs (in-app vs web page vs PDF), it's hard for us commenters to say with certainty whether the decision to remove the "why" was a good call or not.
The Da (Big) / Xiao (Small) prefixes are direct translations of family honorifics that in the simple case directly indicate the relative age of one family member to another. The more common use for family is with more layers of indirection -- so when referring to my mother's younger sister, I would say "Xiao Ai" (Little Aunt), and when referring to my mother's older sister, it would be "Da Ai" (Big Aunt).
In this case I imagine it was more in a professional context, so "Shi Qiang" -- family name "Shi", given name "Qiang" -- was likely elder or the superior of people around them, so would be called "Da Shi" (Big Shi / Boss Shi). If Shi Qiang were the younger, they'd likely be called "Xiao Shi" (Little Shi / Subordinate Shi).
I have found the lowest energy way to shovel snow is to stand with a bit of a bow stance and push the shovel front to back as if you were paddling a boat, pushing down on the end of the handle at the end to launch the snow. Very easy on the back.
If heavier snow, sink into it a bit to transfer more energy.
Works well up to depth of the shovel head, so for deep snow, skim first, and repeat.
For wet snow, launch earlier, but sorry, it’s still hard work.
They're still available in newer forms[1]. Its manufacturer, GlobalScale, is more an ODM for plug computers and provides reference devices.
There are also other smaller full package variants around. I used the Ionics PlugComputers for a PBX project ~8 years ago (no longer manufactured), and still have one of them running a PBX on debian under my desk[2].
Corporate green-washing initiatives like this just make our economic system look good, while doing no meaningful good. These corporations have political power, but they don't use it to solve this crisis.
There are a few of things to be aware of when deploying your own instance in jitsi-meet/config.js:
Firefox simulcast is still experimental (edit: and disabled by default), so Firefox is only sending HD to the video-bridge and no LD stream. The HD is then relayed to everyone even as a thumbnail.
If you don't need to see everyone's video all the time, set channelLastN: 5 or a similar number, and only the last N speakers video will be broadcast
If you don't need 720p (1280x720), change the constraints: video section to be something like 360p (640x360)
Enable layer suspension so that HD is not sent to the server when not needed: enableLayerSuspension: true
There's a large multi-tower project in Toronto that includes a heating and cooling system built by Enwave that incorporates a very large cistern / well, building on their prior success cooling the downtown core: https://www.cbc.ca/news/business/climate-heat-cooling-1.5437...
Besides the physical activities, the number of interested parties that become involved when touching so many things drives up the bureaucracy with each party bringing their own engineering requirements and conditions for cooperation.
reply