Very well done - it took me several attempts to get the hang of Blender and I still only know / used half those shortcuts. Thanks for the easy to use tips!
I think Google has lost all faith in terms of keeping projects around - especially when they involve data locked into a mildly complex system without a complete migration path out.
I would be wary investing time in learning / using any new products from them.
Cyc seemed to be the best application for proper AI in my opinion - all the ML and LLM tricks are statistically really good, but you need to parse it through Cyc to check for common sense.
I am really pleased they continue to work on this - it is a lot of work, but it needs to be done and checked manually, once done the base stuff shouldn't change much and it will be a great common sense check for generated content.
Our ETL process is heavily monitored so we never miss a days data, but we got a surprising error "cant build aggregates - missing data, aborting MV refresh, data will be a day old".
It was the year to date (YTD) calculation - no data for 29/2/2023 to compare to today.
Frankly unless you've considered it ahead of time and thought you'd handled it, IMO you want the error. What's the correct thing to do here? I don't think it's necessarily -365d, it might be, but if I was GP I'd be glad for the chance to consider it and decide what's correct - instead of it just blowing up or even worse silently going whichever way's wrong and undetected for a while.
"You can't capture the CSS that actually makes the page look correct only via the static stylesheets because many of the styles on the page are added dynamically by javascript."
Well, you can - you can have a policy that forces payments from a select group. Some users will complain when "No, you cant pay with 2 chickens every 3rd full moon", but that is too bad.
Of course you then have to be willing to turn down money/customers. As someone who has worked for quite large traditional companies, we've ended up not buying from certain companies because they couldn't invoice us like we wanted to be invoiced.
At least their SQL documentation is public - I remember (at least a decade ago) that only Postgres, MySQL, and MSSQL made their documentation public, while info on IBM DB2 and Oracle was scarce.
In terms of Unreal blueprints they may be low syntax but they are not low code - you still need to know software development techniques or you will end up in a pile of garbage very quickly (which you can also do with any other language).
What is required when using Unreal Blueprints is game development domain knowledge, which makes sense for all those tools, doesn't make them less no-code.
To use Houdini effectively, you need to know vfx and a bunch of other domains, just like you need to understand shaders if you're gonna use the shader nodes in Blender.
All of those things can be achieved with coding as well, and that's the difference. One you write code, the other you don't. Both are backed by code, obviously, but it's hidden from the user but usually extensible by code.
