rizzaxc

I find this usage of AI absolutely brilliant (and ethical): No editorial change or loss of information compared to human reporters, and it vastly improves the accessibility of the information. I think the "voice acting" alone is worth it if you find the visualization off-putting.

as someone who loved maths first but then do programming for a living, it's because solving puzzles is fun. I get the same dopamine hit whether it's a math problem, a coding task, or a video game level. but I think forcing yourself to like something is not the correct approach; you either like it naturally or you tolerate it for some other goals

genuine question; why would you do that lol? phones easily get full day battery nowadays, and flagships get 2 day battery if your usage is anything but insane

i find its biggest problem is its json ecosystem; very clunky and boilerplate-y

I'm not sure if you've noticed, but China make high tech products all the time. ok not semiconductors, but cars, trains, clothings, medicines etc... even social media. maybe they steal some of it, but everything?

the Air doesn't have ProMotion right? that feature is non-negotiable on any display for me nowadays

I'm tempted to try this in my SvelteKit app. What do I lose compared to a React user?

haha is Chinese, so also a "loan" word

how would you do that? once you board people on you can't kick them out; and who would you kick? the fattest ones? also, they need to rebalance with fuel if the plane is overweight. you can't do that with people on board. not to mention finding a scale able to handle a few tons...

SC requires a critical temperature, so the "cooling" part leading to the "producing" part is correct

It's not what the language is for. Go is really strong for greenfield server projects (and bad pretty much anywhere else)

can you explain? to me SOP is feature branch, work there, commit occasionally, then when it's good review, squash and merge (99% of the times done on remote). the history is clean with the ticket ID attached to the final merge commit (as the feature branch is treated as atomic)

if the interviewee would be a direct report of the interviewer, I dont see the issue

this is not true in my experience. they are often 1 or 2 paygrades (literally) below engineers, controlled for ranks