Fred27

I did read it. A compiler converts your code into assembly. They usually have varying levels of optimisation depending on what you're doing.

The article boils down to "could AI be a good compiler" and I'd say that consistency and repeatability are far more important than a one-off optimisation of a particular section of code. If you've got to the point where a section of code is worth writing some hand-crafted assembly then it's probably worth your time to really understand what's happening with it. Having it "vibe compiled" for you would be a bad idea.

Doesn't the compiler rewrite your code in assembly?

My boys (then 10 and 8) loved MakeCode Arcade. I promised that if they wrote an original game - rather than following the great tutorials - then I'd make them a physical setup with a Pi Zero and some classic arcade buttons. They were very motivated and learned a lot.

I agree. I came to Unreal with only a basic level of C++. Having Unreal handle memory management for you was useful, but I can imagine the chaos an Unreal-only C++ developer might cause when unleashed on another C++ codebase.

As a primarily C# developer who has done some game engine work, I recently gave Godot a go for licensing reasons. Apart from some quirkiness I'm fairly impressed. Much nicer C# support compared to Unity. I've done a fair bit of Unreal C++ but to be honest unless you really need the performance that's just too much hard work.

Having said that getting the code working properly with a nice 3D UI is my priority, not having a slick game with some code doing some mundane stuff in the background.

I was born in London, lived in London until about 15 years ago and still go there a few times a year. It really has become as bad as people make out.

One thing that brought it home to me was recently re-watching 28 Days Later. As the main character comes out of hospital and walks over a Zombie-apocalyse London Bridge, I thought "Wow. That looks nice." London in 2026 is worse that Zombie-apocalyse London from 2002.

I found some of these Visionect displays cheap on eBay and was planning to do the same. I found the backend Docker conatiner was unstable and kept crashing so I parked the project. Maybe I'll have to look at it again.

I once fixed a bug with a similar timeframe. Many attempts by many people over the years. One day I finally fixed it and thought I'd let the user who'd raised it know that it was finally resolved. Unfortunately he'd died of natural causes in the meantime. That really hit home how long it'd taken.

Anything that has a "why" _should_ have a comment. I know people like to structure code so that it doesn't need comments. However, nice clean well structured code can describe the _what_ without comments but never the _why_.

I'm not sure the test rides are for the version of the bike with this battery. The bike already exists with a more conventional battery pack.

I've had a brief test ride on a pre-production version of the Verge TS. All seemed OK but I thought the handling seemed weird - maybe due to the rear tyre size and geometry.

I just don't find it interesting. The only thing less interesting is the constant evangelism about it.

I also find that the actual coding is important. The typing may not be the most ineresting bit, but it's one of the steps that helps refine the architecture I had in my head.

I scanned the article to see if "check whether any of their compaints are valid" but didn't see it anywhere. Sometimes maybe the person complaining might be right..

It's a doll, a microbit (with MakeCode) and some double-sided tape.

Tailwind suits the kind of developers who hack things together and build up technical debt and spaghetti code rather thinking about things first and designing things properly.

There's a pizza place in Munich that does the same. It would have been funny if I hadn't been trying to find somewhere my two tired and grumpy kids would agree on for food. One of them was happy to see his favourite pizza on the menu but not happy when he realised the joke.

Now _that's_ what I came to the comments to either see, or say myself.

Korea has a system similar to this. You start at age 1 and get one year older each New Year's Day. https://www.90daykorean.com/korean-age-all-about-age-in-kore...

What's "new" about the interstitium and interstitial fluid? What an odd and pointless article.

I drove round Costa Rica on holiday for 2 weeks. Google Maps worked just fine with destinations (usually hotels/lodges) and I didn't notice anything different about addresses. The roads seemed OK too - apart from some crazy truck drivers. Weird how we had such a different experience.

Canon is off my list. Not only did I have the usual inkjet issues with my last canon multifunction printer, but it refused to scan when it was out of ink too. That's just inexcusably and intentionally bad behaviour.

PHP is useful in the same way that Arduinos are useful. I helps you quickly identify people who don't know what they're doing.

Over the last couple of years I've accidentally done sort of what you're after. I'll describe what happened and give you some thoughts. I'm not sure how useful it will be as I'm now in a business where game engines are used for non-game work and, as I said, my path was fairly accidental.

I took a job doing an interesting C# project where the front-end was being developed by another company (that mostly does cinematic work) using Unreal. It turns out that most Unreal developers love the shiny side of things but rapidly get lost once it comes to needing C++ - or even Blueprints in some cases. I took on the responsibility for the bit where our code meets.

When this project ended, I moved to a different part of the same international company where Unreal was being used for virtual studios. It was a bit of a leap as despite not having much C++ experience, my first proper C++ job was now working on a fork of Unreal's C++ source. That's one huge, unwieldy, undocumented chunk of C++! I sometimes work alongside some very talent Technical Artists who do stuff I couldn't possibly manage in Unreal, but can get stuck when it get down into code. It is more interesting that "standard" dev, but believe it when people say graphics development is harder. In my experience, the only thing that's harder is FPGAs.

Here are some thoughts / tips that might help:

- Get proficient where most game developers aren't - C++. There is some Python used, but good Unreal devs can manage this.

- Use Epic's online learning. Their documentation is awful but their training is good.

- Look at non-game use of Unreal as a stepping stone to game work - virtual studios, architectural visualization, etc.

- This non-game work seems to pay OK. I hear game work doesn't so much. Maybe stay here.

- From my experience, Unity just doesn't seem to have as much traction outside games. Could just be what I've seen though.

I hope these rambling thoughts have been some help.

A Stream Deck (and later a Stream Deck +). Useful and fun to code your own plugins too.

I work 100% remote so I also went for another Elgato product - a ring light - so my work video calls look a bit better. If all of your interaction at work is via video it seemed worth doing it well. My desk now looks more like a YouTuber's but it's all for coding.

I assume it's just an American thing. I'm from the UK and nobody here uses 2 spaces either - and however many we use, it's after a full stop.

Where did you get your 90% for ML stat from? I suspect you just made it up becuase it just happens to fit what you experience personally.

I work with software for virtual studios. It's very similar to gaming in a lot of ways (even using Unreal Engine) and we really push GPUs to the limits. I'd still count this in the "for gaming" category as we;re still rendering 3D scene within a strict time limit.

The flip side is that if someone asks a question like "how do I do X in Windows 10?" there will always be some dull idiot who says "uninstall it and install linux".

Everyone but the OP understands how git works. Removing the file is exactly what I would expect to happen.

If I'm interviewing for a job and they ask me to do one of these tests I just say "no thanks". Any company that puts this sort of HR astrology above technical ability is not for me.

Python is fine as a scripting language, but people seem to forget that it's just that. It amazes me that some people think it's suitable for something like embedded development - in fact there's more than one implementation.

This guy found an interesting way to repeat-but-not-repeat a favourite bit of music. https://medium.com/@alexbainter/generating-more-of-my-favori...