l0gicgate
2.3K posts


@MartinShkreli Use an MD file with a PRD that you draft with some goals. Then use a ralph loop to keep improving it until it reaches the goals you outlined. This is what ralph loop is for.
github.com/frankbria/ralp…
English

@l0gicgate @depression2019 wait, what country is he talking about?
English

@rich_toronto I was over the day Trudeau came in power in 2015. Canada will never be what it once was. The only option is for Alberta to separate and build our own identity.
English

Canada may never have another Conservative government again.
No, I’m not black pilling it. Everything is lining up to for the Conservatives to never win another Federal election, at least for the foreseeable future.
Right now, people are so frustrated and fed up with Canada, they’re leaving. The ones leaving aren’t the ones who vote Liberal. They’re the Conservatives who are tired of watching the Liberals absolutely destroy Canada.
Add to that the floods of people that the Liberals are bringing into Canada. Sorry. Not people. Liberal voters. This will help ensure the Liberals win elections for many terms to come.
This is what I predict the future of Canada will be. Endless Liberal governments until they are so successful at destroying us through immigration, that a Muslim Party is formed and they win a majority government, thus paving the way to sharia law in Canada.
This isn’t just a possible outcome for Canada, it’s a probable one. Look around. You’ll see the signs. This is exactly what is being planned.
And the Liberals are making it happen.
English

@yacineMTB Yea dude. Whoever allowed this should be in jail in perpetuity. Canada is fucking done for. Hopefully Alberta separates and we can put this shithole in our rear view mirror.
English

Our country is entirely overrun
153k is just scratching the surface
Robyn Urback@RobynUrback
From the AG report on reforms to Canada's international student program. Total loss of control, an utter boondoggle, illustrated in one handy chart
English


i found a github repo that lets you spin up an ai agency with ai employees
engineers, designers, growth marketers, product managers
each role runs as its own agent and they coordinate to ship ideas
10k+ stars in under 7 days
1. engineering (7 agents)
frontend, backend, mobile, ai, devops, prototyping, senior development
2. design (7)
ui/ux, research, architecture, branding, visual storytelling, image generation
3. marketing (8)
growth hacking, content, twitter, tiktok, instagram, reddit, app store
4. product (3)
sprint prioritization, trend research, feedback synthesis
5. project management (5)
production, coordination, operations, experimentation
6. testing (7)
qa, performance analysis, api testing, quality verification
7. support (6)
customer service, analytics, finance, legal, executive reporting
8. spatial computing (6)
xr, visionos, webxr, metal, vision pro
9. specialized (6)
multi agent orchestration, data analytics, sales, distribution
what i like about this approach is the framing
instead of one big ai agent trying to do everything, you structure it more like a company. specialized agents, clear responsibilities, workflows between them
im curious to see what this actually feels like in practice and if its any good (do your own research)
github.com/msitarzewski/a…
but as always will share what i learn in public and on @startupideaspod
one thing is for certain and it reminds me
the future belongs to those who tinker with software like this

English

What if a codebase was actually stored in Postgres and agents directly modified files by reading/writing to the DB?
Code velocity has increased 3-5x. This will undoubtedly continue. PR review has already become a bottleneck for high output teams.
Codebase checked-out on filesystem seems like a terrible primitive when you have 10-100-1000 agents writing code.
Code is now high velocity data and should be modeled at such. Bare minimum, we need write-level atomicity and better coordination across agents, better synchronization primitives for subscribing to codebase state changes and real-time time file-level code lint/fmt/review.
The current ~20 year old paradigm of git checkout/branch/push/pr/review/rebase ended Jan 2026. We need an entirely new foundational system for writing code if we’re really going to keep pace with scale laws.
English

@DavidKPiano I don’t understand why LLMs as so prone to doing that in TS code bases. In my repo I explicitly state to NEVER use “any” or “as any” and it still does it anyway. It’s very annoying.
English

@jarredsumner Losing weight without any muscle underneath is a terrible idea unless you don’t care about aesthetics.
Instead, you should try and gain muscle which will increase your metabolic rate and make you look better long term. Not to mention, longevity.
English

@yacineMTB Not sleeping well, not exercising and not eating properly will do that to you. Also signs of a heart attack.
English















