RVS_ParseXMLDuration
daptin
| RVS_ParseXMLDuration | daptin | |
|---|---|---|
| 2 | 4 | |
| 1 | 1,787 | |
| - | 0.4% | |
| 1.9 | 7.7 | |
| almost 2 years ago | 11 days ago | |
| Swift | Go | |
| MIT License | GNU Lesser General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
RVS_ParseXMLDuration
-
Ask HN: Show me your half baked project
Well, these ones aren't "half-baked," but they are no longer being maintained (archived):
[0] https://github.com/RiftValleySoftware/RVS_IPAddress
[1] https://github.com/RiftValleySoftware/RVS_ParseXMLDuration
[2] https://github.com/RiftValleySoftware/RVS_ONVIF
This project is unfinished (I just walked away from it, as it wasn't really giving me what I wanted):
[3] https://github.com/RiftValleySoftware/RVS_GTDriver
This one is "half-baked," I believe. I never really took it particularly far:
[4] https://github.com/RiftValleySoftware/RVS_MediaServer
-
Code Colocation Is King
Not completely. The way that it works for me, is that I start work on a project, and, while building, I notice that some code that I'm working on is:
1) Pretty complex, and fairly insular; and/or
2) Possibly useful, elsewhere.
If that's the case, I will then stop work on the main project, and take some time to extract and "genericize" the subproject. I'll usually set it up as a standalone open-source project; complete with tests and documentation.
This may happen before I have completed the coding in the main project, or may happen as the result of a review, after the fact.
In some cases, I very clearly need to develop a subproject before starting on the main project, or before certain milestones within that project (for example, SDKs or drivers). In that case, the timelines are completely separate.
If you look at my GH repos, you'll see a whole bunch of these projects, including some rather strange ones, like an XML duration parser[0]. These are the types of projects that I extract.
In some cases, I end up not using the extracted project in my main project (happens to some of my UI widgets). In that case, even though I am not using it, I still have an excellent project for the future. Here's an example[1]. I have ended up not using the spinner in my own work, as it was too obtrusive a widget, but it's nice to have it available for future projects.
[0] https://github.com/RiftValleySoftware/RVS_ParseXMLDuration
[1] https://github.com/RiftValleySoftware/RVS_Spinner
daptin
What are some alternatives?
laminarmq - A scalable, distributed message queue powered by a segmented, partitioned, replicated and immutable log.
bramble - A federated GraphQL API gateway
typocide - Where Typos Meet Their Demise!
graphjin - GraphJin - Build NodeJS / GO APIs in 5 minutes not weeks
ukey - Simple ukulele chord reference web app
SeleneCMS - CMS built as a Symfony Bundle
prepareprojectforllmprompt - Transform your code project into a Markdown document optimized for interaction with Language Learning Models like GPT-4, complete with dynamic file selection and token management features.
seleneCMSBundle - Add CMS functionality to your Symfony Apps
speech - A tool to practice English speaking
llm-web - Interact with Large Language Models
quantraserver - Distributed QuantLib
symbiants - Ant Colony Sim + Daily Mental Health Exercises