Apple | Software Engineer - Developer Tools/LLDB | London, UK | ONSITE (3 days/week in office)
The LLDB team is hiring an engineer to work on the debugger, which is used internally across Apple and externally by millions of developers. You'll drive features and improvements in LLDB, collaborating across teams working on the OS and toolchain. Responsibilities range from supporting new hardware and platforms to developing debugging features, with most work open-source (llvm.org & swift.org).
If you're passionate about developer tools with experience in system-level programming and knowledge of compiler/debugger/OS internals, we'd love to hear from you!
Apple | Debugger Engineer | Full-time | Onsite | Cupertino
The LLDB team at Apple is looking for an engineer to work on the LLDB debugger. LLDB is a core part of Apple's developer tools, used internally to debug Apple's software stack and externally by millions of developers. You’ll be able to work on different levels of the stack: from supporting our existing and upcoming platforms to developing new features to make debugging even better. Most of your work will be open source, on llvm.org (http://llvm.org/) and github.com (http://github.com/) where you’ll collaborate with the LLVM and Swift community.
Yes, exactly this. If you have 3 different editors and 3 different languages, you potentially end up with 9 different implementation. LSP means that the same can be achieved by one implementation per language and one plugin per editor.
In addition to what everyone else has said, something I'd find really useful would be going in the other direction. Just mark some keys and it tells you what chord you're playing.
While I agree that there are a lot of bad books out there, I don't agree that programming books suck in general. I very much prefer a well structured book over one of those chaotic tutorials that leave me with more questions than answers. Especially for languages where the "why" matters a lot more than the "how".
> It’s a lot like the way you may have already been doing it, just with more learning.
Maybe that's the reason why I disagree. Indeed, they way I read a book is by putting its content into practice.
From the home and about page it seems like this was developed in the context of teaching a course at the Imperial College London. I wouldn't be surprised if there was just so much bureaucracy involved in getting this open source that the author deemed it not really worth it.
GuardSquare is looking for a software engineer with an interest in software
security. You have knowledge of compiler technologies (LLVM) or the Mach and/or
Linux kernel and you are definitely not afraid of disassemblers or debuggers.
The LLDB team is hiring an engineer to work on the debugger, which is used internally across Apple and externally by millions of developers. You'll drive features and improvements in LLDB, collaborating across teams working on the OS and toolchain. Responsibilities range from supporting new hardware and platforms to developing debugging features, with most work open-source (llvm.org & swift.org).
If you're passionate about developer tools with experience in system-level programming and knowledge of compiler/debugger/OS internals, we'd love to hear from you!
https://jobs.apple.com/en-gb/details/200643284/debugger-engi...