Meal Planner was built for my family, but if it works for us, maybe it'll work for others. You add or import recipes, then manually plan your week, or have AI do it for you.
The @EnglandGolf app just got an update. As a golfer, data is now more difficult to access and read at a glance. As someone who creates digital products, the lack of attention to detail pains me.
It's still very much a WIP, but our Timeline page is our source of truth for current/upcoming work. It highlights what's urgent, what was missed last week, and other jobs due in the week.
Due to lots of client work, it's been a while since I posted any progress on Macaw, our in-house project management system. @millerdup and I have been iterating on it, and we've been able to phase out Linear entirely. #buildinpublic
@49agents@conductor_build@aarondfrancis I seem to have settled on a workflow that works for me at the moment. I grab the feature branch name from Linear, and create a workspace in Conductor with that, so each workspace has a single task. After completion, it's archived.
I've been using @conductor_build for projects that have a lot of concurrent tasks, as the worktree management is great. But I'm going to give Solo from @aarondfrancis a go this morning on Macaw. Previously I'd been just using a terminal window in Zed for that. #buildinpublic
Another simplification that I'm already enjoying using. Jobs initially had a type (issue, task, or bug), but after deciding that tasks should have their own workflow, marking a bug became a toggle. #buildinpublic
Keep on shipping. Added an activity log to all entities in Macaw. Especially useful when viewing jobs, to get an understanding of the journey a job has been through. #buildinpublic
Who defines what constitutes low, medium, or high priority? For us, something is either urgent and needs attention now, or it should be worked on at the right time during feature development.
Some great commits today on Macaw, including a new look to jobs inside lists. @millerdup spoke about how priority scales just don't work for us (or anyone?), so we are going to use an urgent toggle. #buildinpublic
I think there's potentially room for an "assumed" status, where if a contained job moves to In Progress, the job group could be deemed In Progress itself. One to discuss @millerdup
One of the things we've been working on is a re-imagining of sub-issues. Issues with sub-issues just became this odd container purely for contextual information that didn't really deserve a status of its own. So we've implemented Job Groups #buildinpublic
As their name suggests, they serve as a neat container for a group of jobs with contextual information. Job Groups can also contain more info if it's specified.
We already have a basic framework deployed that works well enough to be used to build itself. You can follow the development journey here and with @millerdup, who's handling the spec and QA side of Embark.
. @linear is an incredible piece of software, but it just doesn't work for us as Embark. As an agency juggling many projects across many clients with shifting priorities, the mental overhead of keeping that organised in Linear is real. So we're going to #buildinpublic
Why not, when it's never been easier to produce software tailored for your exact requirements. Something isn't working quite as you want? Update the spec, and have Claude build it out in seconds.