80% of my day to day job has never been pumping out lots of code. it is a complicated career is it? we do a lot of alignment, design and thinking. i can't even agree the idea of outsourcing thinking, i think AI is very good at helping us to think clearly, but it doesn't really "think" for us.
what exactly is going wrong with github aside from all the outages in the past x months? i honestly don't find it particularly disruptive to work/personal stuff. excuse my ignorant, maybe i don't use github enough to know what causes this fury...
fwiw - i do keep a fair amount of code in my computer. i don't push everything..
Just want to comment here. I hate reviewer leave a bunch of nits and stamp the PR. This is ambiguous, are these nits asks or just you opinions? What if I dont address all of them. Also folks need to take rejection lightly - your reviewer wants you to address something, thats really it.
Firstly - Greetings! It’s so rare to see a Clojure person in the wild! and secondly, I really resonated with this! it feels like we, computer programmer, typically overthink too much to begin with, and then LLMs come along and actually help us overthink even more!
was it actually? I don't know the full technical behind this but wiki does suggest: "A search engine called "RankDex" from IDD Information Services, designed by Robin Li in 1996, developed a strategy for site-scoring and page-ranking.."
i argue that most ideas aren't necessary novel, so stealing idea isn't necessary bad.... e.g. i don't think google search was entirely novel, but was well executed.
honestly - meta has built quite a lot of cool things, but c-suite is probably to be blamed for what's going on today.
here's my take - the hardest part isn't doing more computer programming, it is context switching between technical and sales. It has been done, so it is possible, but it is very difficult as people said.
very few computer programmers have good business insight. we know how to build cool stuff, but most of the cool stuff are either - unable to directly bring values to people or cool but no one cares. that's why we need a cofounder, ideally, a person closer to product/sales, who can help you to make connection, understand what people want, shapes product... all the non computer programming stuff.
also - we tend to work in isolation when being the only founder. at least for myself, i sometimes live in my own head, which can be very far from reality...
despite that - i share the same sentiment with you and will not give up trying to found a business :)
(i find)the right way to read a PR can differ a lot from project to project. it's not just about context, or syntax, or workflow...
sometimes the best entry point is the PR description or an external ticket. sometimes you need to read the code first to understand the reasoning behind the changes. sometimes the diff itself is fine, but you have to go back several PRs to see how the codebase got into its current state.
i guess like everyone said here, there no right way to do it.
producing code is just part of the programming, albite a very important part. from my very limited exp, i say programming is more about ...reasoning about behavior, managing complexity, making tradeoffs, handling failure, and building things that still make sense six months later.
AI gets your there faster, but you still need to do the work.
Also think about.. understanding correctness, performance, memory, concurrency, failure modes, and long-term maintainability is another.
companies don't buy anymore, they just take it. think about Claude, every time you use it, you are literally give away your code, your data, and even your personal information.