What a genuinely cool idea.
What a genuinely cool idea.
Management? Gone.
Vision? A hallucination.
Process? LOL.
But thereβs one thing left standing in this flaming wreck of a tech company:
Me. The CTO.
(Miserably employed, but still employed.)
I merge to prod on Fridays.
I deploy through tears.
I write tests in dreams I canβt escape.
Call it burnout.
Call it heroism.
Call it whatever you want.
The jobβs mine now.
The CEO still sends me βquick ideas.β
The investors still ask for βroadmap clarity.β
The interns still log into Figma, for some reason.
But I run this ghost ship now.
I didnβt climb the ladder.
I dug up through the ruins of a startup, clutching a half-written deployment script and a support ticket labeled βURGENT - no context.β
Did I want this job?
No.
Do I know what Iβm doing?
Also no.
But the siteβs still up. The Slack is still haunted. And thereβs no one left to blame but me.
Everyone quit.
The designers. The PMs. The guy who only ever talked about his standing desk.
So guess what?
Iβm the CTO now.
www.miserablyemployed.com/blogs/news/i...
www.miserablyemployed.com/products/hr-...
Wear it to your next "confidential" conversation. Watch the room get real quiet.
I'm the CTO now.
www.miserablyemployed.com/shop/p/im-th...
No budget, no team, no plan⦠just vibes and root access.Designed for founders, freelancers, and the last developer standing. Soft enough to sleep in after a 3am deployment, bold enough to wear while explaining why the site is down (again).
Because nothing says productivity like reading Jira tickets out loud.
www.miserablyemployed.com/shop/p/daily...
That could have been an email.
www.miserablyemployed.com/shop/p/that-...
Vewrite has an integrated editor and a workflow manager, meaning that as you progress through the workflow while doing the actual work, your project management status is constantly kept up to date, too.
Come check it out.
People tend to manually manage these types of projects with spreadsheets or trello or whatever, but that means that you are manually updating the status.
That's crazy.
I've been building a productivity tool for content writing teams called Vewrite (vewrite.com).
The problem that I'm trying to solve is that when you are writing a lot of content as a team you often lose track of the state of things because it is passed through email or google docs (or whatever).
This is awesome. Followed.
Demo of Vewrite's workflow for creating projects and deliverables.
youtu.be/uzTTFwn8ZMU
I guess that's true.
That's a great question that I'm not really sure how to answer. At the end of the day, an LLM is going to have to have access to your docs, which means they should be online and public. Otherwise you need to train your LLM on those docs on the side. I have no expertise with that.
Let's take a long, hard look at why Vewrite is built the way that it is.
We dive deep into what structured workflows are, why not using them is dangerous, and what Vewrite's default writing workflow is.
vewrite.com/articles/why...
#writing #content #contentcreation #devrel #marketing
Reading documentation is a skill that can be learned. Let's talk about how to do it effectively so that you retain the most knowledge in the shortest amount of time.
www.ramijames.com/thoughts/rea...
#developers #devrel #documentation #technicalwriting
I just think that technology will outpace biological improvement.
I'd prefer a cybernetic future, but I worry that the most likely outcome there is deeply integrated surveillance and ad-tech in our bodies and minds. Full control by those whose incentives do not align with our own.
We've been experimenting with improving how our beta testers actually get their work done with our product. We've done a write-up going through the product process, illuminating how we think about what makes for a better integration between workflows, states, and the content produced.
Take a look!
Being confidently stupid is an addiction.
Anytime someone in charge gives a blanket statement that "x group are lazier and dumber than another", it's a play to turn the groups against each other so the person in charge can take advantage of the situation.
Or maybe they are camping the name. I dunno.
You need to be able to actually use it to understand if the experience is correct or not. It's ok to throw away development work if you find you've gone down the wrong path.
I think that you should be making functional experiments and not clickable prototypes as part of your development process. It's not enough to just have a design that gives you an inkling of how it will feel.
I think my favorite thing there is that topics don't really bleed over. I'm almost never recommended posts or people that aren't relevant to me. That means I never see political content, which I'm really grateful for. I see a lot here on BS and I'm just really over it.
Will do :)