I have a Vue3 started template I host at https://http://vue-template.spaghet.me/ and all I have to do is curl and I'm ready to go.

Showcase:

https://timer.spaghet.me/ https://colors.spaghet.me/ https://box.spaghet.me/ https://talk.spaghet.me/ https://farming.ope.cool https://stitch.ope.cool https://draw.ope.cool https://walz.ope.cool

I feel like I get asked a lot the same questions and I think this article describes it best. Like yes I could have just upgraded to a nicer printer, but there is something fun about the process of getting an artwork plotted that makes it fun for me.

I need to upload some of my plots to share.

---

On a similar note for others who want to get into this, there was a thread awhile back on "What is the 90% activity in your favorite hobby", for example sanding taking 90% of the time for woodworking. For pen plotting the 90-95% is the art side. Taking images, converting them into g-code either via SVG or other processes, or writing code to make generative art, that is the 90%.

At the end of the day the pen plotting itself at the surface level is a projection of the effort taken to generate the art. Where it gets really exciting is the capabilities and unique aspect of the medium (like touching on white ink or watercolor) that create truly unique ways of presenting the art.

--

Some related subreddits:

https://www.reddit.com/r/PlotterArt/

https://www.reddit.com/r/PenPlotters/

I think it follows a few topics, "the art of the POC/Spike" or just exploratory coding. These things give us a tangible hands on approach for understanding the codebase, and I think lend to better empathy and understanding of a software system and less rash criticisms of projects that may be unfamiliar.

This is particularly relevant to me right now as I am discovery coding a fairly large project at my company and working with product to lay out design and project planning. Whats difficult to express from my current standing is how the early stages of these types of projects are more milestone / broad based rather than isolated small key pieces. Sure I can spend a week delivering design, architecture, epic, outline docs for all the known and unknown features of the project (and I am). But at the same time I need to discover and test out base case / happy path solutions to the core business problem to more accurately understand the scope of the project.

I think its something I particularly love about being a TL / IC at my company. I have the flexibility and trust to "figure it out" and the working arrangement to provide adequate professional documentation at the appropriate time. I am fortunate to have that buy in from leadership and certainly recognize it as a unique situation.

All that being said:

1. Learn how to effectively isolate and run arbitrary parts of your system for YOUR understanding and learning 2. Make it work, make it right, make it fast. 3. Learn to summarize and document your findings in a suitable fashion for your situation 4. Encourage this throughout your team. Useful in all aspects from bug triage to greenfield work

Migrated away from Swaggo -> oapi during a large migration to be interface first for separating out large vertical slices and it’s been a godsend.

I personally use SQLite and DuckDB daily, but recently adopted turso in lieu of litestream for a something. I appreciate that they all are relatively compatible but I'd love to just have a tool.

Even then thats why I love the relationship between SQLite and DuckDB. I can backend my system with SQLite and run analytics and processing via DuckDB and they service specific purposes.

The hard thing with this for me is being a split consumer and not having the bandwidth to split my attention between who is doing better innovation and just using a tool I can rely on to predictably get the job done for me.

That being said, hats off this is awesome. I really appreciate turso.

I personally have some side projects that have started as X, transitioned into Y and Z, and then I stole some ideas and built A, which turned to B, which a requirement in my professional job necessitated the Z solution mixed with the B solution and resulted in something else which re-ignited my interest in X and helped me rebuild with a more clear mindset on what I intended in the first place.

All that to say, these things are dynamic and a long list of "failed" projects is a historical narrative of learning and interests over time. I love to see it.

https://youtube.com/@justinthetrees?si=FCKrfjddLS7f8U2i

I have tons of little single HTML file sites I make from this [Vue template](https://vue-template.spaghet.me/). I also have sites just published as public Notion docs, inline photo libraries from iCloud, etc. Its amazing how easy and available it is to just connect stuff, and how often I want to over complicate things and build something from scratch when I can just link stuff together.

On an aside I also love things like [mmm.page](https://mmm.page/) for quickly stitching together little micro sites or single use sites if I don't have time to do something else. Its fun exploring all these tools

https://vue-template.spaghet.me/

I am biased, I worked for Capital One out of college for 4 years as a software engineer and had a wonderful experience. It was the best place for me to learn industry and professional engineering, and I felt the company culture / company itself was a fantastic place to work. So respectfully I disagree.

I couldn't find any pricing info, but I would test drive one for a work setup if I had the chance.