Last month's exclusive video at The Spicy Web demonstrating a CodePen example of Signals—what they are, how they work, and why frontend frameworks and fans of vanilla #JS alike are adopting them rapid-fire—is now available to view for free! Check it out:
Provocative statement. But not unexpected given the rise of #LargeLanguageModels and their ability to transform one language to another. In fact, this capability exists now and is being built into products, increasing productivity and sprint velocity.
How are you leveraging these technologies to realize the same benefits?
#TodayInHistory 1984 - Ashton-Tate introduces the dBase III relational #database program for IBM PC-compatible computers.
dBase was one of the first database management systems for microcomputers and the most successful in its day. The dBase system included the core database engine, a query system, a forms engine, and a #programming language that tied all of these components together.
A clean Git history is the key to successful teamwork and quick bug fixes. Errors can only be successfully tracked down if it is always possible to trace when and where code was changed by whom and for what reason.
🥴 However, in the rush of the battle, the changes that are packaged in a commit are sometimes not taken very seriously. Who has never experienced this? A change that is actually unrelated to the current work package has made it into the commit because the file has already been saved temporarily.
💡The solution: With an "interactive add" (git add -i), you can pack partial changes ("hunks") into a commit and specify line by line what should be included in the next commit.
Sometimes when tweaking things that are very sensitive, such as audio generation or physics systems, I just play around with parameters for a while, sometimes getting cool results, sometimes screwing up, quickly saving and testing as I go.
Then I feel like going back to something I had earlier, but it's hard to reproduce it. I don't have a great solution for that yet, maybe I should just have a mode where I commit every save to git or something?
Does anyone else do that?
Then if I hit the situation from the video where there are new commit(s) on the remote, #git stops the merge and displays a message. At that point I can decide how to handle it.
I'm working on a #programming project (#opensource) and I want to make a post about it on #HackerNews.
It is functional and works quite well for having started work on it recently. Should I just make the post on HN?