markoa

Looks interesting, starred, thanks.

For me the prerequisite for leveraging openclaw was developing function oriented repositories of markdown files tied to my roles that capture pretty much everything I know about the subject and ongoing work, and working with agents as assistants off of those as context. As a founder, product manager, for growth etc.

From there it’s pretty natural that I wanted to talk to an always on agent not tied to any particular machine which has the same context plus access to google drive etc.

1/ Use a standard CSS library - Tailwind

2/ Use a common React component library such as Radix UI (don't reinvent the wheel)

3/ Avoid inventing new UI patterns.

4/ Use Storybook so you can isolate all custom UI elements and test/polish them in all states

5/ Develop enough taste over the years of what is good UI to ask CC/Codex to iterate on details that you don't like.

One thing that I'm sure of is that the agentic future is test-driven. Tests are basically executable specs the agent can follow and verify against.

When we have solid tests, the agent output is useful and we can trust it. When tests are thin or missing, the agents still ship a lot of code, but we spend way more time debugging and fixing subtle bugs.

iOS Liquid Glass needs its own Snow Leopard.

Like any CLI Claude Code should follow decades old tradition of providing configurable verbosity levels, like tcpdump's -v to -vvvvv to accommodate varying usage contexts.

We're looking to add more AWS resources, k8s, ssh, Cursor... tracking it publicly here https://github.com/orgs/superplanehq/projects/2/views/17

Love this, bookmarked.

The solution, as always, is doing more of what you want to see in the world. Maintain a personal blog and post more from the heart.

in case anyone’s curious about the context of the protest, I wrote a brief summary for an outside perspective about a month ago https://markoanastasov.com/signals/serbia-student-revolution...

For me the sentiment is even stronger, further amplified by the presence of AI. Big reason why I started a personal blog around New year.

Yes, managers should make an effort to explain the optimal way and steer the conversation. But also people who are in an individual contributor role can simply get ahead of the game by learning the difference.

Is ChatGPT involved? :)

IMO one of the founders must be the chief growth hacker. Hiring people to delegate execution of details is easier. Curious about replies.

Semaphore | Remote | World-wide | https://semaphoreci.com

Semaphore is a leader in cloud-based CI/CD, with over 50,000 developers relying on it to test and deploy their code. Our mission is to help product teams ship their software faster and with more confidence by providing a robust and scalable platform for software delivery.

We're hiring Software Engineers (junior to senior), UX/UI Designers, Technical Writers, and Project Managers: https://apply.workable.com/semaphore/

Semaphore | Full-Time | Remote | https://semaphoreci.com

Build an industry-defining product with a great team.

Semaphore is a leading CI/CD platform for testing and deploying code. Our customers are companies across more than 100 countries, from tech industry heavyweights to startups just about to make their dent in the universe. They all need their products to move as fast as possible — and Semaphore enables them to do that.

All Semaphore careers - https://apply.workable.com/semaphore/

Learn more about us - https://semaphoreci.com/about

Currently open roles:

* Developer Evangelist

* Director of Content

* Head of Customer Success

* Marketing Project Manager

* Technical Writer

* Senior Product Designer

I was lucky to inherit a Zenit camera with a macro lens. I have been shooting with it for ~10 years now and am still mesmerized by the photos it creates. My old Flickr page has a couple of examples: https://flickr.com/photos/manastasov/4985941953/

SEEKING FREELANCER | REMOTE

Semaphore (CI/CD service) is looking for developers who blog to join its new community authorship program. Topics are all about building, testing, and deploying code. Your articles will appear on https://semaphoreci.com/blog and reach an audience of at least 30k developers. We pay per article.

If you're interested, reach me directly at marko // renderedtext.com. Include links to your best writing.

Semaphore | Software Engineers, Linux System Admins | Full-time | Remote (European time zones) | https://semaphoreci.com

Do you want to help build the world's best CI/CD product? Join us https://apply.workable.com/semaphore/

Semaphore CI/CD | Technical Editor | REMOTE | Full-time | https://semaphoreci.com

Semaphore is looking for someone who is passionate about helping software engineers write and share their knowledge with the community.

The ideal candidate has a hybrid background in software development and writing/editing.

Learn more and apply at https://apply.workable.com/semaphore/j/17003BBCA0/

Co-author here. Working on a CI/CD platform and seeing how real teams actually build their apps, I can tell you that the majority are still not using containers.

It ain't easy. It changes the entire build/test/deploy process. But it is the best way to build for the cloud.

So we wrote this book for developers who need to get things done. Hopefully it's a good mix of required fundamentals for a practical reader, and realistic examples.

I'd love to hear your feedback, and any particular questions or struggles you've had while transitioning to containers.

Semaphore CI/CD | Senior Engineer | Full-time | Remote https://semaphoreci.com

Semaphore helps developers ship great products at high velocity. We're a bootstrapped remote company, you'll be working with a high-performance international team and have a real impact. https://semaphore.workable.com/j/7899071CEA

We're hosting an open global Zoom call for all engineers affected by the outage, join us at https://zoom.us/j/793450725

Semaphore 2.0 offers 1,300 minutes (disclaimer: I'm a cofounder, so you can also AMA).

Here's a lengthy interview with John Arundel, an author of the book: https://semaphoreci.com/blog/2019/02/14/a-reality-check-abou... You can get a lot from it without giving away any of your personal or fake information. :)

If you don't mind logs and project pages not being publicly visible, you can start using the Semaphore 2.0 free tier with your open source project. If you run out of credits send a support request and we'll increase.

That community page is outdated and referring to Semaphore Classic (1.0) and 2.0 will be getting proper open source support soon.

Thanks for mentioning Semaphore, cofounder here. Yes, we’re 100% bootstrapped and in this for the long haul. It’s really all about execution. We built 2.0 in a timeframe in which we’d previously ship one or two features. Of course years of domain experience help, but everyone from Fred Brooks to DHH is right — adding more people won’t help build a better product faster.

It sounds like you don’t have a total budget for your startup, broken down into target spending per month and a deadline when you expect to either get even, raise an investment or quit. Maybe start with that? By having a plan you prevent constantly questioning what to do and leave more energy for creative work.

We host our company playbook as a collection of Markdown files in a GitHub repo.

Thanks for using Semaphore Mike. Have you tried the new 2.0?