41–50 of 81 posts
You can take it a step further and strip out the frontend. Honestly. Nobody needs it and if you need any UI stuff it in the MCP. This is what I did with this project https://github.com/crmkit/crmkit/ and to be honest the approach grows on me and fits well if you are a backend person.
You can take it a step further and strip out the frontend. Honestly. Nobody needs it and if you need any UI stuff it in the MCP. This is what I did with this project https://github.com/crmkit/crmkit/ and to be honest the approach grows on me and fits well if you are a backend person.
What are people's workflows these days? As I use claude more and more I've started using git worktrees, one branch per worktree per PR, with possibly multiple agents working in each worktree at the same time on different aspects. And I manually instruct those agents. Like Emdash/Cursor/Zed. Sometimes I review code locally, sometimes agents push and I review in GitHub, no clear system yet. (jj seems promising, but Zed…
https://github.com/Paca-AI/paca/security
However I'm getting a 404
https://github.com/Paca-AI/paca/security/advisories/new
(You need to enable private security advisories: https://docs.github.com/en/code-security/how-tos/report-and-..., really not sure why GitHub made it opt-in only)
We're using GitHub for everything here, but was using Jira as an email first helpdesk.
Was hoping this was that - but apparently not at all.
We almost went with libredesk - but it's a little too simple (no merging tickets?). We're giving FreeScout a go - looks like we might need the oauth2 plugin to work with o365 mail ...
[1] https://www.joelonsoftware.com/2001/03/23/strategy-letter-iv...
> A lot of software developers are seduced by the old “80/20” rule. It seems to make a lot of sense: 80% of the people use 20% of the features. So you convince yourself that you only need to implement 20% of the features, and you can still sell 80% as many copies.
> Unfortunately, it’s never the same 20%. Everybody uses a different set of features.
-- Joel Splosky
You can take it a step further and strip out the frontend. Honestly. Nobody needs it and if you need any UI stuff it in the MCP. This is what I did with this project https://github.com/crmkit/crmkit/ and to be honest the approach grows on me and fits well if you are a backend person.
I like the direction! But why stop with CRM functionality with very limited schema for tasks on the headless when OP has a lot more to offer there? Why stop at CRM plus Project Management then? Why not also schemas for ERP, HR, finance tools and all other business software? And we even bother with a custom made API when PostgreSQL and PostgREST could reduce the full thinking to the database schema?
The next evolution for this is to allow users to use the AI to change the database schema itself. Like if someone is using our restaurant software and wants to start selling merch. I’d want them to be able to use the AI to change the database schema and add products and shipping from the e-commerce one.
I really do think that is the future of SaaS. You start from a base SaaS and the AI customizes it to your business over time.
https://www.atlassian.com/platform/teamwork-graph
Their skills abuse your context window and billing, you'll want to write your own for the 20% you use