1. You can see them in my recent submissions. Don't want to shill.
156 karma · joined March 20, 2011
1. You can see them in my recent submissions. Don't want to shill.
I always thought there was a business in making that consulting easy to find. Its usually a very hard thing to find good consultants.
I prefer to manage my worktrees manually with a super simple script.
IMHO, the codex desktop app is very powerful for development + testing given it can easily control the computer.
I guess what I relate to the most is how dismissive people get about real software engineering work.
I may have skill issues, but I am yet to reach the level of autonomous engineering people tend to expect out of AI these days.
What an awesome journey!
1. faster more configureable action runtimes so I can get faster builds 2. usable merge queues because the github one is a joke 3. some reasonable CI management and workflow debugging features
I guess I can overcome the "what if I cannot undo" anxiety.
[1] https://getcook.dev [2] lazygit
Really? it took "user feedback" for one of the world's best software companies to realize one of the most fundamental parts of the OS was broken?
I have been long on $MSFT for a while now, but my faith as an investor stands shook.
[0]: https://news.ycombinator.com/item?id=47262711 [1]: https://getcook.dev
People are flooded by new projects and assume (rightly) that most are low-signal, so they don’t engage. Because there’s low engagement, new projects get even less visibility. That reinforces the belief that nothing interesting can be built anymore.
I ship earlier now (often free and open source) to learn faster, but it doesn’t change the attention dynamics much.
The bottleneck isn’t building. it’s distribution and who already has an audience. Now dont get me started on getting an audience. thats a whole different pain.
Pains I faced running BIG clusters on-prem.
1. Supply chain Management -- everything from power supplies all the way to GPUs and storage has to be procured, shipped, disassembled and installed. You need labor pool and dedicated management.
2. Inventory Management -- You also need to manage inventory on hand for parts that WILL fail. You can expect 20% of your cluster to have some degree of issues on an ongoing basis
3. Networking and security -- You are on your own defending your network or have to pay a ton of money to vendors to come in and help you. Even with the simplest of storage clusters, we've had to deal with pretty sophisticated attacks.
When I ran massive clusters, I had a large team dealing with these. Obviously, with PaaS, you dont need anyone.
Thank You for an amazing product!
Overselling abilities is for sure a lack of quality.
And this is the case across the board.
My friend's Fitbit works way better than my Apple watch.
Third and final example is how bad Apple's native dictation engine is. I can run OpenAI Whisper models on my Mac and get dramatically better output.
As a long time Apple fan who's had everything since before the first iPhone, I feel this apathy towards product quality cannot be disguised as some strategic decision to fast follow with AI.