@MrPeterLMorris Can probably get away with parenthesis cast and FQN import
static bool Parse(string s) => (bool)new https://t.co/T0Dvv6dRkQ.DataTable().Compute(s, "");
@MrPeterLMorris Or if you want to make use of the fact you are in a JVM. Supports the full syntax of the above version.
If you want to change the rules to use &&, || and !, you can remove the .replace lines.
They are doing this to attract people who want to use AI for scripting. Visual scripting and AI are not a good combination.
They are banking on the people who will use AI for scripting and become new customers will outweigh the number of existing customers that they will lose.
Epic has always chased the asset flippers, even before AI. Advertising better graphics, free megascans, getting big devs to switch over to their engine by waiving the fees etc.
If you are a software engineer who’s three years into your career: quit now. there is not a single job in CS anymore. it's over. this field won't exist in 1.5 years.
- Hacker steals Claude agent
- Hacker uses Claude to hack
- Hacker pivots to compromised server
- Hacker uploads Claude (with logs) to server???
- We investigate compromised server
- Full agent logs detailing hacking recovered 😅
AI agentic hacking deep dive: 50 servers, 14 companies, all the prompts, tools, attribution...
There is a growing trend in the data space to use LLMs for every problem. In 99% of cases this is a bad choice.
Don't use a sledgehammer when tweezers will do.
https://t.co/8ywb8Z9gdL
@rfleury@mitchellh@wagslane For UI/UX (and games), getting a user to use your app/play your game while you silently watch is 100x more valuable than trying to dream up BS metrics.
There is a problem space where unit testing is the right choice, for example I would argue a standard library be tested with unit tests, but in the vast majority of cases I would agree.
Unit testing is just another tool in the toolbox. Sometimes it is the right choice, sometimes it is the worst choice possible.
Unit tests suck at testing interactions.
If you have a large deterministic system a snapshot test is the answer. If you have a non-deterministic problem space precision/recall/f1 (or sort of loss function) is preferable.
Property based testing is also sometimes the right answer. For example if you are testing an encryption implementation you will get way more mileage out of running : decrypt(encrypt(x)) == x 10k times on random x's than encrypt(x) == "random_cipertext".
There is so much more nuance than unit testing = bad
The demo for Order of the Sinking Star, the *huge* puzzle game we've been working on for a long time, is free this week on Steam...
Playable only during NextFest, it'll be gone after this week, so check it out if you're interested!
https://t.co/z4KE9ENEEc