samstress

No, but... is the better answer in my mind. Learning to code is a considerable commitment. It takes years to get good enough to produce professional-grade software. If you extrapolate from the improvements we've seen in coding AI over just the last 12 months, this is just a bad allocation of your time.

Instead, as the article points out, learn to become a translator between the real world and AI code generation. Learn about industries that are relatively underserved by technology. Don't build tools for developers or engineers. Learn about construction, mining, waste management, oil and gas, manufacturing, logistics, government... then become the link between that industry and AI's ability to add value.

(Emphasis on relatively underserved — all of these have high-tech versions in some places, but the future isn't distributed evenly.)

My thoughts too. Isn't much of the appeal of Apple to non-developers that it just sorta works without you having to think too much about it? That means that Apple necessarily just makes decisions on your behalf.

If they'd allow for more fine-grained control of low level aspects, a lot of their plug-and-play promise would no longer apply.

One room even features a secret entrance — hidden inside a rocket by the pool. — Ey — pshhh! :-)

I used to live in the inner city of Leipzig during my university days, and we had a door in the basement that led to wartime tunnels connecting it to other houses. It wasn't like a massive maze, just a hub with three other paths, each leading to another house nearby. From there, however, if they'd unlocked their doors, you could travel farther.

I was on a mission back then to befriend and convince random neighbours across the street to open their access doors and get some kind of network going, but I didn't meet with much enthusiasm.

I'm genuinely curious — do people really prefer this HTML-style syntax like

  <LinearGradient colorA="#0f172a" colorB="#7c3aed" />
  <CursorTrail />

I appreciate that React & Co. have established it as a standard. I've used A-Frame lately, which lets you build WebVR components, and even there you declare your scene as

  <a-scene>
      <a-box position="-1 0.5 -3" rotation="0 45 0" color="#4CC3D9"></a-box>
      <a-sphere position="0 1.25 -5" radius="1.25" color="#EF2D5E"></a-sphere>
  </a-scene>

and I feel this is getting a bit much. Wouldn't it be better to have a JS API that lets you define objects and properties and compose your shader / scene etc. programmatically? (I've seen that Shaders offers that too — just asking in principle.)