Wooooo
Rate Sheets are in general beta for Noko! nokotime.com/rate-shee…
See how you’re doing in 2023, and make sure you’re spending your work time on the most valuable projects
Which, upon reflection, is reaaaallllllyyyyyyyy fuckin shitty after the Super Bowl
Listening to Off The Wall for the first time, uh, and 2010s Justin Timberlake was really just copying the answers over MJ’s shoulder, wasn’t he?
The UJS pattern that Rails has (had? The Rails JS & documentation story is messy) is arguably the best bridge that’s been implemented between client & server.
It can be rigged up with basic data attributes, it is powered by the browser’s native event-handling. That makes it easy to extend/customize, it doesn’t get in your way, and there isn’t a deadly tight coupling between the client & server codebases
I’m BEGGING any competent iOS/macOS developer to build a competitor to TextExpander. It’s so damn clunky for no reason, the iOS keyboard straight-up doesn’t work, and their Electron UI is garbage. I’d pay a subscription for a replacement in a heartbeat
Yes I am 12
In a day of firsts, I also got my first YouTube review! youtu.be/fhmF-HnJp…
I hadn’t fully internalized some of the points he makes about my music, but hearing it said out loud there’s definitely stuff that’s right on the money
Also “this might be drier than usual” - is the story of my life 😂
The corollary of this software architecture discussion I posted a few weeks ago is that you’ve gotta be consistent about it.
In this week’s case, it means begrudgingly realizing “well, hell, this actually needs a rewrite.” Even though I’m not looking forward to it; it’s 100% going to help by reducing the number of hacks & simplifying the codebase.
Kept going to refresh & try to find @ivory@tapbots.social today on the App Store, subscribed to Premium. A mixture of excitement at a first-class Mastodon client, & seeing an indie developer get back up after the Twitter shitshow
I wish someone had told me punk would involve so many glue sticks & cardboard
🤯 this experiment paid off, it’s actually in a record shop. Now to wait and see if it sells 🤞🤞🤞
Graphic design is my passion
Graphic design is my passion
This was a great insight into the crucial roles that make communities thrive overcast.fm/+k8ijTRj9…
I wanted to post this yesterday, but I got food poisoning (don’t get food poisoning).
I figured out a physical release for Mesh Network! DIY, made from recycled materials, cost-effective.
Cursed food poisoned idea.
A parody of the Barenaked Ladies banger, “Yallternative girlfriend”
Been a busy day, but finally sketched out the idea I had for how record shops could add digital-only releases into stores. I don’t know if I’m missing something, but it feels like a no-brainer?
Does anyone know of record stores that sell digital-only stuff (eg: bandcamp releases)? I had a brain blast on how it could work, but curious to see if/how stores are already doing it.
Any ambient internet radio stations want to add “Mesh Network” to their rotation? It’s a meditation on what a grounded solarpunk future could be like.
tcannonfodder.bandcamp.com/album/mes…
#music #solarpunk #ambientmusic #internetradio #bandcamp #indieartists
To save you a 10 minute YouTube video: here’s how to neatly organize your analog synths without losing any data & allowing for customization later
To save you a 10 minute YouTube video: here’s how to nearly organize your analog synths without losing any data & allowing for customization later:
- Create 1 MIDI track, 1 audio track
- Combine them into a track stack, with a descriptive name
- SAVE YOUR PATCH NAME IN THE TRACK NOTES. This is crucial
- Play around in the MIDI track, record your performance, get it just how you like it
- When you’re ready to record; switch over to the audio track: press record, get some coffee, come back when it’s finished
You keep all the MIDI data; you can tweak + re-record as needed, and you don’t lose what patch you used!
Compounding effects of good software architecture
Noko since 2021+ has proven this thread 1000%
The compounding effects of upgrading to current Rails, crystallizing our 14+ years of product lifespan into an actionable framework on top of Rails, keeping that framework declarative & straightforward, and making sure any new code fits in said framework means that we’ve been able to ship stronger features, faster.
- Rails 7+ gave us Arel, Scenic, and JS importmaps, and ActiveModel
- Those became the foundation for building clean layers, keeping our model code simple while allowing us to flourish in our UI design & tackle performance problems.
- That meant we could rebuild the reporting engine from the ground up, with ridiculous performance
- The simplicity of our framework means that we can build out standard components with minimal overhead
- Which made tackling giant things like the Timer easier
- Which gave us the knowledge + skills to build out rate sheets in ~month
- And means that we’re able to keep hammering at quality-of-life features (like calendar syncing) in record time.
- All amidst a dozen other tiny product things!
Reading the docs, refining, and enforcing frameworks is an actionable way to get to dependable foundations
The past 2 days have been a march of package regressions, merge conflicts, and environment hiccups. For a relatively straightforward environment!
Glad we focus on keeping things as simple as possible.
Want to try something: AMA about Mesh Network! Process questions, inspiration, etc.