Mostly Grey former ginger with a preference for Rust. Leads wg-rustup, sorry about the mess. He/Him or They/Their Now @kinnison@fosstodon.org too
Manchester
Joined December 2008
- Tweets 12,967
- Following 105
- Followers 493
- Likes 1,386
What would you prefer as a structured data format which isn't entirely awful for humans to interact with? The condition I place on it is that as a human I'm not made sad. json, xml, toml, all make me sad. (YAML makes me _less_ sad, but not happy).
1
Pff, I'm still waiting for a new delivery window for a 'next business day' delivery from UPS which was posted on Tuesday.
I could say the same about Rustup :D I look forward to hearing the results fo your experiment in bounties :D
1
Heh, I've been following Zeeshan's work long enough to know I'm unlikely to fix anything scary :D zbus is very clever stuff.
1
Perhaps "If you have to ask what a full stack developer actually is, you are one" is the definition then?
3
Sadly in the 'real world' it tends to mean "Can write a web UI, but can also work on the API service which it talks to, and probably write the SQL schema that service uses" It makes me very sad.
1
To me, a full stack developer can at least *understand* and *modify* anything from VHDL/Verilog through bootloaders, kernels, low level OS code, middleware, services, UI, servers, etc. Also some ability to read/adjust schematics and hardware layout.
To a webdev, who knows?
1
1
That's mostly due to my own stubborn idiocy though :D I slept in an additional 2.75 hours this morning :D
This is why I spend a bit longer on my AoC solutions than many (I never get on the leaderboard really) but I try and write code I *can* come back to and understand later.
1
Once again, @ericwastl made getting up during December that much more fun. Thank you for #adventofcode2020 Eric, and for those that went before.
300 club membership ahoyhoy!
9
I suppose if you're allergic to docker (I wouldn't blame you for that) You could just do it as Ansible, but that's not quite the same idea.
1
Well, your docker could combine all the tooling, a webserver, etc. And give you an "easier" to re-deploy container later. Rather than a set of cobbled notes to try and redo next time. I only think of it as essentially executable notes for deployment.
1
1
Sounds like a reason for you to write a Dockerfile :D Time to learn the horrors. Let them gaze into your soul.
1