In the middle of migrating very old, homegrown tomfoolery into a more modern stack. Fun and vexing at the same time. This codebase has all of the bad decisions. All of them.
@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerswrote:
Maybe implementing a subset of Markdown would be a good thing. I am thinking about bold, italics, inline code, and code block, mostly. Oh, and links.
I agree that minimalism is hard. Thatโs why the subset was explicitly recommended small. Yet, I believe it is extremely useful to have.
@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerscontinued:
I've tested MD and honestly I don't like it. Bold/italics add unnecessary noise/clutter and the font is already monospace, suited for code, so inline code & code fences are not needed. If 3rd party clients want to implement them it's fine but I'm sensitive to visual noise.
I agree with this. The core you're building is around a deliberate minimalist philosophy. I was happy to build an opinionated client for my own use-case, but it should imo stay on the fringes for those seeking it.
I laughed at this. I'm all for people crafting their own tools, but it really feels like everyone's reinventing the same handful of wheels for agentic development.
Having a little difficulty seeing how long this service will exist. People are terrible. Sooner or later it will be found and ruined.
@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyersreplied to@crustyrustaceanprofilefollowOld school metallian, hobbyist developer writing things mostly in Rustโฆmostly:
Yup. I have long change my philosophy on things like these: just live the day. :-)
While learning jj, I realize how Git habituated me into being ok with its unique jargon and prickly command line interface.
Unlearning Git is refreshing.
#jjnotesfollow is just brilliant; it really feels like theyโve fixed all of the problems with git whilst at the same time remaining completely backwards compatible. The simpler interface, the universal undo, the reduced set of concepts โ Iโm a big fan
Also, editing and rearranging commits like 3x5 notecards on your desk is tremendous. It makes using an SCM feel more like editing your work than lumbering forward.
Finally watched Project Hail Mary. Easily one of my top 5 favourite films but itโs still not nearly as good as the book โ I feel like the cut some pretty important scenes
I loved the book and Iโm always fearful when a movie script is developed and a movie produced, so my relief after I saw the movie was immense. I too feel theyโve cut-out some bits, but the main thing that a book almost always takes my breath away with is fueling my imagination. A movie would (possibly) never nail that aspect.
I just watched it as well. It was fun. There were a number of things that I felt weren't explained well and broke my suspension of disbelief; I haven't read the book, but I found myself really curious whether the book takes the time to justify things more. Obviously, the movie has a lot of pressure to rush to the next "big moment".
If thereโs one thing Andy Weir canโt be critiqued on then itโs not fully justifying all of the science. I think the film on the other hand can be hard to follow for someone who has neither read the book nor has a scientific background. Itโs just hard to monologue about gravitational forces and relativistic speeds on screen.
I've spent way too much time recently writing TUIs for productivity (eg. merging github PRs, Google Chat DMs, firewall approval requests into one dashboard, another for watching actions on my PRs) and lost a lot of productivity as a result.
I empathize, we've had that happen within the last year too, even the same bathroom-over-kitchen floor plan.
And the extra test of patience: the kiddos don't have the skills to properly clean and sanitize that kind of mess.
Might be a good outcome to this. Water remediation folks want to take out 30 sqft of drywall to ensure the space btwn floors is fully dry. But my architect father-in-law thinks this is yagni and we can get away with just using a fan and space heater to let it dry out on its own ๐ค
Thankfully, the zero cost option seems to have worked out. Had fans pointed up at the ceiling for a couple days. Will have to patch up some water-damaged drywall, but think we can avoid opening up the ceiling ๐
Feel like we got lucky in this case. Maybe we'll find out in 10 years that we have wood rot thanks to not shelling out for the professionals ๐คทโโ๏ธ
Spent months pair-building a full telecom BSS with an AI. The surprise wasn't the code โ it was that the real job became verification. The AI read 450 tokens for every 1 it wrote. Turns out building honestly is mostly re-reading.
#opensourcebssnotesfollow
Is open source dead?
Everyone has the power now to make their own stacks of things.
The people aspect of open source is dead or dying. I don't think the bunny is going back in the box.
One nice thing about Open Source (at least for me) is different people doing the same thing in different ways and one of those happen to suit my taste perfectly. And in many cases, I won't be able to come with it myself even with Super Intelligence.
Evgeny Morozov has pointed out that using ai through chat interfaces is based on an individualised and privatised model, which (heavily paraphrased) is inherently anti-social.
With an extra layer now of people making small personalised tools, do bigger things still need teams of people who know what theyโre doing?
FWIW Iโd like to see more sharing of vibe coded tools instead of everyone making their own more less the same ones. Mine are here: pauladams.neocities.org
I don't think so. I have been using more open source software than ever before.
You may argue that with LLMs I have the power to make my own stack of things, but this doesn't eliminate that I still need knowledge to properly steer an LLM to create something worthwhile.
If I have no knowledge of what I intend to build, the best thing the LLM will generate is a half-assed copy of something that already exists. Which is what we have been drowning in the past couple of years.
AI can be a superpower in the hands of someone knowledgeable. That makes the people aspect of open source more important, not less.
If you offload your curiosity and desire to learn to AI, you will be a slave to it's limitations instead of being a master of its capabilities.
Of course not. I think it is much more relevant to ask "Is closed source dead?".
Anyone can now replace a proprietary program with a vibeslopped alternative which might suit them just as well. It will have the same level of trust (ie. none) and none of the other drawbacks.