I'm just not convinced by this article. XSLT was a great technology in its time, but these days if you need to transform data into markup, modern templating engines are just way easier to use. I've said it before on HN: Being able to transform data into markup natively in the browser with a declarative language is still a neat idea. I enjoy thinking about an 'alternate future' where the web evolved in this direction instead.
What is this measure defending against (other than getting a job)? The recruiter can still extract the information in your signed PDF, and send their own marked-up version to the client in whatever format they like. Their request for a Word document is just to make that process easier. Many large companies even mandate that recruitment agencies strip all personally-identifiable information out of candidates' resumes[1], to eliminate the possibility of bias.
1: I wish they didn't, because my Github is way more interesting than my professional experience.
I live in Australia, which is culturally the polar opposite of Germany[1], and you'd get a similar response here. If the police saw it, you'd be fined at least $500, and risk losing your licence.
1: Australia is very egalitarian, rather than hierarchical. Pragmatic, rather than bureaucratic. Australians are direct and emotive communicators. Spontaneous planners, etc. etc.
In Southern Europe, not many people wait for a red light if there isn't anything to wait for. Even the police blasts through red lights if nobody is using the pedestrian crossing.
Sydney has an extensive network of toll roads, and it's a nightmare. The state government has outsourced the initial infrastructure development to a private company (Transurban), who pay off their development costs through collecting the toll. It costs taxpayers a fortune. Sydney's road network is so poorly designed that it's difficult to get anywhere without crossing a toll road if you actually value your time. People allege that the state government is deliberately designing bottlenecks into the road network to funnel traffic into toll roads (e.g. westbound traffic on Parramatta Road) and it's difficult to disagree with this assessment. I live in the city and most of my driving is for leisure, yet somehow I still paid $850 in tolls over the last 12 months. Just in case anyone is wondering, there's no 'toll plaza'. Our toll roads have an automated collection system which operates via ALPR.
I always wonder why these guides stick to x86(-64). I get that it's still the most popular processor architecture for desktop computing, but it's got a lot of complex legacy baggage that's an unnecessary cognitive burden for beginners. It's also a relatively uncommon target for real-world bare metal development. Why not target RISC-V? I've done a lot of OSDev in both x86 and RISC-V, and I think RISC-V is much more teachable. You don't want to bog the reader down trying to understand what protected mode, or the A20 line is, when you could just focus on more universal concepts.
This project started because I wanted to understand the linux that sits on my computer, which is x86. There is a possibility that on the future it will have multiple architectures supported, probably starting with arm, but I can't promise that
My next step is documenting how all of the subsystems work (such as virtual memory, allocators, drivers, etc.), then lay the project to rest. I don't have any grand ambitions for the kernel. The project was just a labor of love, and a way to learn some interesting things! Hopefully some of the documentation can serve as learning material for other people interested in osdev.
Remote: Yes
Willing to relocate: Potentially
Technologies: Node.js/Typescript, PostgreSQL, MongoDB, AWS, .NET, React(Next.js, Redux), C, Rust, Ada, and more...
Email: ajxs@panoptic.online
https://github.com/ajxs
https://ajxs.me
reply