VP Engineering, @juliacomputing. Author, Julia High Performance. Finance - Programming - AI.
- Tweets696
- Following139
- Followers871
- Likes289
ALT Screenshot of Workshop Abstract - Introduction to Julia Tuesday 19th July 14:00–17:00 (UTC) This workshop is geared towards anyone who wants to start using Julia. It will be an extremely accessible overview of Julia. We'll cover how to download and install Julia in Windows, Mac and Linux. Next, we will show how to use Julia in the terminal (REPL), in VSCode, and also in an interactive notebook with Pluto. We will contrast Julia with Python, showcasing major differences and also comparing Julia to a popular beginner's language such as Python. Additionally, we will teach how to install and uninstall packages. The bulk of the workshop will be how to run Julia commands, what are statements and an overview of the Julia syntax. We encourage everyone that wants to know more about Julia independent of skill-level to join us.
ALT YOU WILL BE ADVISED TO STOP WRITING CODE OR ENGINEERING. ✨ FUCK THAT. ✨ Everybody’s favorite hobby is hassling new managers about whether or not they’ve stopped writing code yet, and not letting up until they say that they have. This is a terrible, horrible, no-good VERY bad idea that seems like it must originally have been a botched repeating of the correct advice, which is: STOP WRITING CODE AND ENGINEERING IN THE CRITICAL PATH
ALT Can you spot the difference? It’s very subtle. Let’s run a quick test: Authoring a feature? ⛔️ Covering on-call when someone needs a break? ✅ Diving on the biggest project after a post mortem? ⛔️ Code reviews? ✅ Picking up a p2 bug that’s annoying but never seems to become top priority? ✅ Insisting that all commits be gated on their approval? ⛔️ Cleaning up the monitoring checks and writing a library to generate coverage? ✅ The more you can keep your hands warm, the more effective you will be as a coach and a leader. You’ll have a richer instinct for what people need and want from you and each other, which will help you keep a light touch. You will write better reviews and resolve technical disputes with more authority. You will also slow the erosion and geriatric creep of your own technical chops. I firmly believe every line manager should either be in the on call rotation or pinch hit liberally and regularly, but that’s a different post.
