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.
If I've approved the PR, then these are changes I'm asking you to do, but not ordering you to do. You are free to say "no" to my request
> What if I dont address all of them
Then you will have decided that you don't agree with my recommendation and that's OK.
I only ever do this with people I trust - I am trusting you to review each of my nitpicks and make an informed decision if they're necessary or not. Generally I'd like you to reply to the ones you don't do with a reason though.
On Github, there is a way to leave individual comments in the code and in addition give a review a summary.
In addition to hitting the "approve" button, I typically spell it out explicitly in this summary: "Please check my comments and see if anything makes sense to implement."
Often, I also take this opportunity to point out the "one" most valuable change in my opinion.
If the developer of the code doesn't find any of the comments to be applicable/usefuly, they can always go ahead and merge it right away.
I try to tag the line-by-line comments with little labels like [Unimportant] or [Style] so that someone going through them has an idea of their (un)importance without reading the whole thing.
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!
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.
No the strategy of having a professional looking social space in the web, specifically focused on college folks solely was novel - this is what he stole and without this it wouldn’t have gotten to the place of success it is today. Knowing about the technology is no good without a solid strategy - with a solid strategy anyone can raise the funding to go build it. It’s easy to know what to build when you have a vision specifically of what you’re building into.
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.."
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 :)
Yes, switching between development and sales/marketing is probably the hardest aspect for me.
Most years I have a booth at an industry trade show. For a couple of weeks preparing for it, the week during the show, and a couple of weeks after that, following up with potential customers I met at there, I find it virtually impossible to get an development done.
Also, onboarding new customers with my software is usually labor-intensive. So that also takes time from development.
(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.
Great point and that's our takeaway too from talking to many users. We're exploring ways for Stage to possibly tailor the review flow to each specific PR/user preferences. Would love to hear any ideas if you have any!
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.
fwiw - i do keep a fair amount of code in my computer. i don't push everything..
reply