182 karma · joined February 14, 2020
AFAIK one can flash a Yubikey with a specific AES key and make the Yubico backend aware of that AES key. The OTPs won't start with cccc but something else then (this is used to differentiate from the default flashed AES which is already known by Yubico).
So what's stopping you from flashing the same AES key to another Yubikey, essentially duplicating your key (at least for OTP)?
This is of course not as secure as the initial AES known by Yubico and present on your Yubikey (not readable).
Then, the battery could be a lot smaller and the device would be sleeping most of the time.
That's possible since e-ink only draws power when updating.
Therefore, when code changes, the documentation might tell a different story.
Documentation-as-code (i.e. doctests in Rust or Go) alleviates some of the shortcomings by showing how to use an API correctly.
The beauty of Docs-as-Code is that parts of it can even be generated. I'm thinking Diagrams-as-Code where the system under test can be i.e. queried for capabilities.
To be clear, I think integrated/integration tests in their own only add value if you have a couple of them (meaning <5).
Otherwise, they're red and no one knows why. And they take a whole lot of time to execute.
JBRainsberger has an nice talk on them [1].
Pactflow have implemented a Contract/Collaboration framework called Pact [2]. I haven't used it professionally but I love the concept.
Absolutely.
> 2. Sprints aren't a failure of agile, they're a failure of devops.
I don't think so, here's the timeline: Scrum (90s), Agile (2001), DevOps (2009). So sprints have been around a long time before DevOps, the way I interpret it.
> 3. Estimates aren't literally the devil, execs need to have a rough idea how big it is, just don't get more granular than months
How? Your event horizon spans only the next couple of iterations, everything beyond that is pure speculation.
Countless times I had to estimate Jira "tickets" (actually called issues in Jira terminology) in hours. To this day, I fail to understand why and I haven't gotten a pertinent answer other than "the business needs it for planning, they're paying us, so you do it."
Yet this contradicts at least 2 Agile Manifesto pillars:
1. People and interactions over processes and tools (fostering the estimation ceremony + booking time rather than actual interaction or developer happiness).
2. Reacting to change over following a plan (plan-the-work and work-the-plan over reacting to change).
How do you even "do" estimates?! Clean Agile (ISBN-13: 978-0135781869) says "Estimates are never commitments. They are guesses."
So it seems the business is trying to get a commitment out of an estimation, at hour granularity.
What are your thoughts here?
Do you tell a painter to get it done by Monday?
That's why small iterations are there in the first place: to constantly add incremental value, not "big bang" plan-the-work and work-the-plan but reacting to change.
Not sure what you mean by that. These languages are not managed ("not garbage collected"), but certainly not low-level programming.
There are services written in them.
To your original Q: what's more important for you? Experience or money?
If money is more important for your life phase (marriage, kids, house, etc.), learn in your free time.
Code in the form of a test is.
It shows how you can interact with the system/component/unit under test.
Is it better to implement something natively in a compiled library and link it in from Java or better to rewrite it in Java? What about lifetimes of objects - who "owns" an object - the runtime or the lib?
That's why the focus on certifications is absurd, imho, not Agile itself.
> [..] if your organization is struggling with an Agile transformation, drowning in chaos, you’re going to leap when someone offers you a lifeboat in the form of certifications and processes and tools. Executives understand processes and tools much more than they grok self-organizing teams.
[1] https://www.simplethread.com/agile-at-20-the-failed-rebellio...
This is clasically done via memory synchronization mechanisms/atomics.
Reading an issue I've opened almost 2y ago [1], seems the backend requires the client to have a specific gcc version.
That's a strong limitation imho.
[1] https://github.com/bazelbuild/bazel-buildfarm/issues/545
I see the linked resources are to docs only.
If it's any help, here's a bazelized Rust demo implementation:
https://github.com/mihaigalos/code_templates/tree/master/rus...
Empathy is essential.
Check out Bazel for Rust.
It allows:
* caching of artifacts.
* shareable caches between {developers, build jobs} based on hashes.
* remote distributed builds (on very many cores).
But in most cases, you would use a driver and abstract away what individual registers get read/written. The HAL can be taken from anywhere, really. Doesn't need to be avrgcc/Arduino.
The registers in the link are C macros resolving to uint8_t*, pointing to memory locations where you read/write to.
Very small current draw, particularly in sleep mode (picoamps), otherwise good enough processing power up until 32 Mhz. The craft is complex because it requires both software and hardware (electrical engineering) knowledge for just about anything more than blinking a led.
It's fascinating in its own, when things work. When they don't (faulty wiring, lack of electrical contact, etc.), it's very frustrating.
> Is it simply that AVRs are available in through-hole packages?
Perhaps, for small projects. If you go a bit more advanced, you can order PCBs very cheaply online (5$ for 5 pcs).
> Are they perceived to be easier to start with, compared to small ARMs for instance?
In the end, you write code for a compiler so from your perspective, nothing changes.
If there is enough work doable by AI, why would humans still be needed? Some humans would cover the missing 10% of what AI can't do, as pointed out in other threads. But that leaves a lot of humans idle.
The entities operating this AI would still need to operate i.e. in a country. So the country's government will have to enact some sort of legislation to regulate the AI's impact.
It doesn't necessarily mean everybody will be out of a job and miserable. Probably work would be optional and shelter, food and the likes would be provided by the government.
So new (same-)old development then?