izabera
Joined 11 years ago
Karma
549
Submissions
85
Member since
Jun 21
Joined 11 years ago
this is literally like every other app or cookbook
- other team opens jira ticket requesting a new type of encabulator
- random guy who doesn't know anything of how the current encabulator system works picks up the ticket for whatever reason
- 10 minutes later opens a 2000 line vibe coded pr with the new encabulator type and plenty of unit tests
- assigns ticket to the person who designed the current encabulator system for review
- encabulator system designer finds out about this ticket for the first time this way
- "wait wtf what is this? why are we doing any of this? the current system is completely generic and it takes arbitrary parameters?"
- waste an hour talking to the guy and to the team that requested this
- explain they could just use the parameters, close pr and ticket
it's so incredibly productivei ran `source /path/to/timep.bash; timep ./cube.bash "R U R' U' R' F R2 U' R' U' R U R' F'"`
without profiling https://i.imgur.com/JE93ony.png
with profiling there's a bunch of errors but overall it's ~300x slower https://i.imgur.com/qif7Qp3.png so i'm sceptical on all the efficiency claims
likewise, suppose you buy a 1gb plan from a mobile isp, then you find a youtube tutorial that you're interested in. the nugget of information you need is 23 minutes in, but you have no way of knowing that upfront, it may not even be there. you can exert some control over how many bytes you send in the headers of the get requests to youtube, but you have little control over how youtube compresses the video you requested. also you download 2 30s ads and a sponsored segment before finding what you were looking for. unfortunately you're now out of data on your plan. do you blame your isp for their shady sales practices? is it youtube's fault? what did you pay for?