diff --git a/config.toml b/config.toml index 3dd6112..f3e9a8c 100644 --- a/config.toml +++ b/config.toml @@ -4,7 +4,7 @@ title = "Arenzana" theme = "hack" paginate = 10 -copyright = "© 2021, Ismael Arenzana. All rights reserved." +copyright = "© 2022, Ismael Arenzana. All rights reserved." pygmentsstyle = "solarized-dark" pygmentscodefences = true @@ -17,7 +17,7 @@ summaryLength = 20 [permalinks] blog = "/:slug/" - + [params] subtitle = "" disableDisqusTypes = ["page"] diff --git a/content/posts/2022-01-11-emacs-rust.org b/content/posts/2022-01-11-emacs-rust.org index b4c0c07..1832aa0 100644 --- a/content/posts/2022-01-11-emacs-rust.org +++ b/content/posts/2022-01-11-emacs-rust.org @@ -8,7 +8,7 @@ #+TITLE: Emacs for Rust Development * Emacs > Visual Studio Code -There's a good chance I'm a hater or that I don't know what I'm doing. After a couple of hours trying to set up VS Code for Rust development, I ended up frustrated not understanding how to simply call the compiler or the debugger from the interface. I looked for ~rust-mode~ on Github and 15 minutes later I was up and running on Emacs. Maybe it's my previous experience with [Go](https://arenzana.org/posts/2019-12-03-emacs-go-mode-revisited/) development set ups that made it all quite simple. +There's a good chance I'm a hater or that I don't know what I'm doing. After a couple of hours trying to set up VS Code for Rust development, I ended up frustrated not understanding how to simply call the compiler or the debugger from the interface. I looked for ~rust-mode~ on Github and 15 minutes later I was up and running on Emacs. Maybe it's my previous experience with [[https://arenzana.org/posts/2019-12-03-emacs-go-mode-revisited/][Go]] development set ups that made it all quite simple. * Rust on Emacs I approached this the same way I approached Go: let's get regular syntax highlighting, linting, formatting, and compiling first and we'll worry about debuggers later. I'm a bit old school when it comes to approaching debugging. @@ -32,7 +32,7 @@ We end up with the following on the Emacs config (if you use ~use-package~): :hook (flycheck-mode-hook . flycheck-rust-setup)) #+end_src -Here, we load the mode for Rust development. Auto-indent with spaces, run ~rustfmt~ on save (needs to be installed via [rustup](https://rustup.rs/). Prettify symbols (cause why not), and use language server protocol. I'm binding "M-," to compile; I know it's an odd keybinding, but I'm used to it by now. Feel free to make it your own. +Here, we load the mode for Rust development. Auto-indent with spaces, run ~rustfmt~ on save (needs to be installed via [[https://rustup.rs/][rustup]]. Prettify symbols (cause why not), and use language server protocol. I'm binding "M-," to compile; I know it's an odd keybinding, but I'm used to it by now. Feel free to make it your own. In addition to this, I'm hooking ~flycheck~ for linting. @@ -40,5 +40,3 @@ In addition to this, I'm hooking ~flycheck~ for linting. IntelliJ made it very easy to set up as well, but that's a multi-hundred dollar application. If you're on a budget, Emacs, vim, or VSCode should bet viable options as well. I'm still getting started with Rust and I don't know how much it will stick, since I've been writing Go for a number of years; but I'm happy I have a familiar environment to get started from. By now I should know Emacs should *always* be my first option. - - diff --git a/static/README.html b/static/README.html new file mode 100644 index 0000000..a233f12 --- /dev/null +++ b/static/README.html @@ -0,0 +1,168 @@ + + + +
+ + +Hello! This is Isma and this is my README. If you're reading this, +you're probably reporting to me. You can think of this README as sort of +a first approach to my management style, what you can expect from me, +and what I expect from you.
+I have a mixed operations/software development/business +background, with formal education on the last two. I can easily talk all +day long about all three of them with little authority on +either.
I was born and raised in Spain and this fact may be reflected in +the way we interact: expect passionate (but respectful) work-related +discussions and polite smiles to American football remarks. As a good +European, expect me to wear scarves during the winter.
Spanish is my first language, English is not. I want to apologize +in advance for any misunderstandings. I am very aware of cultural and +linguistic differences and I'm intentional about making sure communication +is fluid and misunderstandings rare.
Part of my work is to facilitate yours. This includes answering +questions, make resources available, and filtering out noise coming down +our way.
+Due to the nature of our work, I value quality over quantity, and +that will hopefully be reflected in the workload I assign to you. That +being said, if you feel like the quality of your work is being +sacrificed by the load or deadlines assigned, I expect you to let me +know.
+I expect excellency from you. That is not to say "perfect code" or +"perfectly monitored systems", but going the extra mile to do your best +work. If you're a developer, code should be tested. If you're an +operator troubleshooting an issue, a root cause is expected rather than +a simple restart. As a team, we want to take pride on the work we do for +public safety.
+Every line of code we ship (or don't ship) has an impact of people's +safety. Unavailable or incorrect location could potentially be fatal to +someone's life. We need to treat every service and every release with +this thought in mind. If you have questions about the quality of a +release, element, product, you are expected to bring it to my attention +(even if it's my own doing).
+You are always welcome to come to me with questions. Be ready to +explain the research you have done, approaches you have taken and +solutions you have tried to come to a solution by yourself. If all those +have failed, I'll give you guidance or work with you help you come to a +solution.
+All feedback is welcome. This is what you need to know about it:
+I will do my best to put myself in your position and will understand +it comes from good intentions with the goal of building me up rather +than bringing me down.
Even though directness is not in my nature, I will strive to give you +the best feedback possible.
+Disagreement is feedback and the sooner we learn how to efficiently +disagree with each other, the sooner we’ll trust and respect each other +more. Ideas don’t get better with agreement.
+You can expect to meet with me on a one on one basis every two weeks. +To me, these are the most important meetings of the week and I hope you +can find value in them too.
+These are not status update meetings. We have other meetings for +that. If you feel like you want to give me a status update on something +or have a quick project-related question for me, you can tell me at the +beginning of our meeting.
+The goal of these meetings is to make sure we are on the same page, +for you to know where I think there can be improvements, and for you to +let me know where I may be falling short. Feel free to bring any +HR-related concerns/issues you may have. I may not be able to resolve +them for you, but I can either guide you or intercede on your behalf if +necessary.
+I work a bit some weekends. This is my choice. I do not expect that +you are going to work on the weekend unless there is a public +safety-affecting issue or production work that cannot be scheduled any +other time. I might Slack you things, but they can always wait until +work begins for you on Monday. If something urgent comes up, I will text +you/call you.
+Likewise, feel free to Slack me after hours. I may or may not respond +depending on availability and/or notification settings. If you have +something urgent to escalate or bring to my attention, you can reach me +at +1 (260) 797-6529.
+I take vacations. You should, too. Disconnected from work is when I +do some of my best work. Not taking vacations, invariably leads to +burnout and can negatively affect the team.
+Using MXGuarddog for spam software
-Using Runbox for email hosting.
-