This specifically isn't illegal though. They've only scraped public repos.
I could use two &mut [T] values, built with split_at_mut, but this is unwieldy.
This is likely to be the best option. You could wrap it in a nice interface that provides normal indexing but panics if you index the forbidden element. AI will be able to easily write that code for you.
and even if one has to do such a refactoring what is the point of using YAML at all ?
It allows the CI engine to determine which jobs to start, what their steps are etc.
To be fair I have worked on one project that had very complex CI and we almost decided to generate the CI graph procedurally with a Python script (Gitlab supports this, somewhat awkwardly). But in the end we decided it wouldn't be worth the overhead of writing, maintaining and learning a whole new CI system on top of Gitlab's CI.
You can (and should!) do exactly the same with "traditional" GitHub Actions style YAML.
Avoid putting commands in the YAML - put those in separate scripts and call them from the YAML. The YAML should only be used for things that can't be done from scripts (e.g. job matrices, uploading artifacts, reporting status etc.)
Seems reasonable but good fucking luck enforcing that.
IMO they should instead simply charge cost price for hosting. It can't be much surely?
I totally agree about story points being bollocks. Their supposed justification is that you can measure velocity by seeing how many story points you do per month, but that only works if there's no feedback from velocity to story point estimation which is obviously not the case.
So in practice they just become a stupid proxy for time. "1 story point is an hour right?"
The Fibonacci thing makes some sense to me though - it is a way of suggesting that bigger estimates are less accurate.
Of course it would be much better if you could actually put an accuracy directly into Jira or whatever (e.g. 10-30 hours), but that would apparently be way too complicated. You could also get that data fairly nicely from planning poker (which I also think is pretty good, but you throw away all the information about uncertainty that you just spent ages discovering!)
Well I guess not everyone learns at the same rate.
All it takes is one internet search with the words “zig style guide” to find countless examples to pull from online.
"Countless"? You should be able to find, say three style guides that talk about how to prevent memory errors then right? Because my one search didn't find any.
Yes. It's not as easy and reliable as Zig.
There are definitely some cases where memory safety isn't especially important:
- Single player games
- Apps that don't process external data (e.g. a simple calculator).
- Lots of things running on microcontrollers, where the form of input could never possibly cause any security issues. E.g. a motor controller or a basic syringe pump or a (non-smart) washing machine or something.
- Tests, e.g. I've considered writing RISC-V tests in Zig. They're traditionally written in C or assembly.
In cases like those, memory unsafety mainly leads to non-security bugs and annoying debugging sessions. But I wouldn't say it's as much of a deal breaker compared to e.g. writing a video codec or font renderer or web browser or DNS server or whatever.
I still think Rust is a better choice than Zig in most cases anyway, even ignoring memory safety. But in these cases it's at least a defensible choice.
C won’t surprise you...
Lol... I'm sure there's a meme or graph for where you are in learning C to believe this.
then translates to assembly code with a very predictable pattern.
Even this is a stretch. Modern C compilers can do some wild transformations. I assume you've seen the classic one where UB makes it jump to a function that you never actually call.
bash scripting is well-defined
Yeah I mean Bash's problem isn't that it's poorly defined - it's that the definition is awful!
C is firmly in the "not fun" camp with PHP, JavaScript and Bash. I'd say even assembly is more fun, in a puzzle challenge sort of way.
The most fun language I've used is QuakeC, because the only thing you can do with it is write Quake mods. It was a pretty neat language too from what I remember. It even automatically detected infinite loops!