is ultrasonic scanning completely harmless for developing baby? when my wife was pregnant, I remember they wouldn't recommend too frequent ultrasonic scans...
Ultrasound is totally harmless, but doctors recommend ALARA ("as low as reasonably achievable"). Average baby is exposed to 50 - 90 minutes of ultrasound over three visits, though we had to go more frequently for scans for all three of my kids. This would be 36 minutes if you went in every week. If it was possible to get medical quality anatomy scans and avoid transvaginal scans (either because of the tech or simply just going reguarly enough to catch all the imaging you need) then it would win the entire US market for sure: roughly $3-7B for the ultrasounds (3.5M US births at $1-2k per for ultrasounds). also it's a spa -- prenatal wellness spend in the US estimate at $5-7B.
if there're some specific tests/evals to satisfy that an agent can test by itself, it can easily iterate for hours. And this time also includes running those tests/evals, which may not be small.
Their point is that OP used the same dot separated phrase to point out that there's a 0.8GB model and an audio/image model on device. Which reads weird.
imo, it really depends on what you enjoy doing. Regardless of AI, choose software development if you like to build complex systems that no-one has built before, and have enough patience to dig deep / debug things to make them work exactly as you expect.
For some of us here, it's just what we love to do, no matter what tooling is available. When I first started building my own software long time ago, it was a very slow Basic and fast raw machine codes (in octal system, PDP-11 like CPU). I enjoyed it not because of tooling, but despite of it.
Over the years, the tooling was getting better in general, which allowed us to build increasingly more complex systems.
With AI, we will still be creating & debugging. It's just that before AI, I had to spend 90% of my work on mechanical not-so-fun things to get things to work, and only 10% on fun algorithmic-intensive parts. But with AI tools, this ratio seems to change, and all kind of boilerplate code & algorithms can be written much faster by AI, hopefully leaving more time for us to work on creative part of the work.
I heard they do CS exams on air-gapped machines at UC Berkley. Use of AI to do CS homework is strongly discouraged, and if someone cheated, it shows up at the exam...
I guess if I were in school today, I would be accused of using AI on my homework, as I did very well on all of my projects and bombed my tests. My professors all recognized my hard work and gave me good grades, but I feel like that wouldn't go the same way today.
In theory yes. They've got a bargaining chip with TSMC. But it's unclear how much use that would be without a safe shipping route between Europe and Taiwan and/or a navy capable of maintaining such.
> First git itself is distributed and built for scale.
there're different dimensions for "scale" - like handling large monorepos, orders of magnitude more commits, tighter requirements for latencies (for agentic use, e.g. for agentic history navigation)...
There're tons of ways to fine-tune WebRTC that it wouldn't corrupt audio in poor network - it has all of the controls to smoothly trade-off latency vs quality. Not just NACKs - FEC, disable PLC/Acceleration/Deceleration, larger JB (tons of parameters) etc.
Most of the glitches I heard with OpenAI's Voice were not WebRTC related - but rather, to my ear, they sounded more like realtime issues with their inference - which is a very different component to optimize.
reply