The bottleneck was never the code
thetypicalset.com
The bottleneck was never the code
1–10 of 446 posts
Re: The bottleneck was never the code
#2Re: The bottleneck was never the code
#3(not related to the article)
The flashing red dot on the web page is very annoying. Is there some design reason for that?
edit: I meant the inside `trail-map-container`
Re: The bottleneck was never the code
#4Can someone explain the title? I think the author illustrates that the code was the bottleneck and it has shifted to context. What am I missing?
Re: The bottleneck was never the code
#5If thats true, I am sure some C-suite manager knows this already. Assuming management knows what they do, after all, they're getting payed for this. The time where engineer are trying to educate people above them should be over. Management gets payed for the big decisions. If they tank the company, so be it. I no longer care.
Re: The bottleneck was never the code
#6(not related to the article) The flashing red dot on the web page is very annoying. Is there some design reason for that? edit: I meant the inside `trail-map-container`
FWIW I see the red dot only at the top of the page, flashing slowly. It does not annoy me, in fact I only discovered it because of your comment.
Re: The bottleneck was never the code
#7(not related to the article) The flashing red dot on the web page is very annoying. Is there some design reason for that? edit: I meant the inside `trail-map-container`
I think he's going for a metaphor about groups versus individuals. There are other gray dots around the red dot. Software is a group effort, but made of individuals. Something, Something.
Re: The bottleneck was never the code
#8I think the argument here misses critical nuance; there is a difference between code used to implement a product and when code _is_ the product.
It goes without saying that agents have little to no product sense in any discipline. If you're building a game or an app or a business, your creative input still matters heavily! And the same is true for code; if the software is your product, then absolutely the context missed by skipping the writing process will degrade your output.
That doesn't mean that writing code wasn't a bottleneck even for creating well structured software projects. Being able to try multiple approaches (which would have previously been prohibitively expensive) can in many instances provide something a room of bickering humans never would have reached.
Re: The bottleneck was never the code
#9(not related to the article) The flashing red dot on the web page is very annoying. Is there some design reason for that? edit: I meant the inside `trail-map-container`
From what I can tell, it marks the article you're on. There are other light grey dots with other article names in it.
Re: The bottleneck was never the code
#10I think the argument here misses critical nuance; there is a difference between code used to implement a product and when code _is_ the product. It goes without saying that agents have little to no product sense in any discipline. If you're building a game or an app or a business, your creative input still matters heavily! And the same is true for code; if the software is your product, then absolutely the context mis…
> difference between code used to implement a product and when code _is_ the product
Care to elaborate? I don't understand the difference unless you mean code that _is_ the product, being OSS code or code for license.