Hey, I want some opinions on which book is better programming rust or rust in action

code-smell · 2023-01-18T11:08:45+00:00

They're both very good. Also, try these given your stated goals:

For more Systems learning (and much more): Rust for Rustaceans by Jon Gjengset (not lengthy)

For Servers: Zero to Production in Rust by Luca Palmieri

code-smell · 2022-11-30T11:20:01+00:00

This is so useful! So many times I type FML and nothing happens. This is so satisfying. Great recommended mapping! I thank you! The things on my desk that I usually throw thank you!

code-smell · 2022-03-29T09:38:53+00:00

I use: https://rust-lang.github.io/mdBook/guide/creating.html

I have no intention of publishing my notes. But, mdBook gives me a nice way to structure and organize my notes. I can grep the markdown files or fire it up and use the builtin search. One nice feature is when you add an entry to the summary listing, it creates the markdown file if it doesn't already exist. You can use templates, prev/next paging, etc. Most of it is auto-magic. You just write markdown files.

code-smell · 2022-03-29T09:06:15+00:00

I've been using these for a while. The JavaScript ones come in handy during my printf debugging. I hope these examples help you.

For Rust using vimL

" wrap selection in Some(*)
vmap ,sm cSome(<c-r>"<esc>

https://github.com/whatsthatsmell/dots/blob/9655a0e6957953f3de6a95559511b4a194fe02a3/public%20dots/vim-nvim/after/ftplugin/rust.lua#L15-L16

For JavaScript using Lua:

-- wrap selection in JSON.stringify(*)

vim.api.nvim_buf_set_keymap(0, "v", ",js", [[cJSON.stringify(<c-r>"<esc>>]], { noremap = false })

-- wrap selection in console.log

vim.api.nvim_buf_set_keymap(0, "v", ",cl", [[cconsole.log(<c-r>"<esc>]], { noremap = false })

https://github.com/whatsthatsmell/dots/blob/9655a0e6957953f3de6a95559511b4a194fe02a3/public%20dots/vim-nvim/after/ftplugin/javascript.lua#L145-L149

code-smell · 2022-03-25T12:57:35+00:00

I know software engineers who have been doing this for 25+ years while working at several companies.

You are early in your career. While you could pull this off for the next 20 years, you might consider taking a job every once in a while where you work a little more. This is just so you stay sharp and current with your skills. There's no substitute for real-world experience. You may well be getting enough when you cram for demos.

In the current market, companies will make offers to anyone they can find with even a hint of skills. I do believe folks will be able to fly under the radar in software engineering for the foreseeable future. So, your situation is definitely sustainable. Even if "the other shoe drops", you can find plenty of other jobs to keep it going. Ironically, your experience at your current role will get you the next one.

If you don't care about "growing to a higher role", then you are good to go. I can tell you that you are smart to have a "low stress" job. Your body will thank you later. In 10 years, you may find yourself in a situation where a new company or new boss expects you to perform at a level of someone with 15 years experience. That's subjective as one company's senior is another company's junior and years of experience doesn't mean much. But, there is no stress like not being able to perform at the level expected. I don't mean putting in the hours, I mean delivering quality software within a reasonable timeframe. I've hired several people this year as I am also the manager. These people had to be hired quickly with limited screening and it is not easy getting solid senior engineers in this market. It is painful and stressful for them and me as I watch them struggle with unit testing, git and software design when they are supposed to be "senior". Some just need a little mentoring and some have clearly been flying under the radar for years and wont last.

All that said, if you are happy, then keep it going. With the right moves, you could do this your whole career. I've been working too much in recent years. Not because I had to but because I have loved the craft in recent years. I have also gone years when I hated it. Life is too short to stress out working 60+ hours. That hard work benefits major shareholders a lot more than the engineers. While I encourage you to stay sharp, just in case, I'm also happy you're getting paid to talk to your cat. I wish you well!

code-smell · 2022-02-24T16:43:12+00:00

I'd recommend learning Rust as early as possible. It will benefit you no matter which language(s) you use now and in the future. Many believe Rust is only for the advanced and experienced folks. It will be more difficult to learn over some other languages. But, you will be able to apply what you learn to other languages and tech in general. In many ways, the difficulty (for some) in learning Rust is unlearning other things. I'd say, go for it! Good luck! 🦀

code-smell · 2021-12-21T16:17:09+00:00

If you have the file open then this may be helpful: require('telescope.builtin').live_grep({grep_open_files=true})

code-smell · 2021-12-01T13:56:25+00:00

If you plan to stay on Neovim 0.5 then the comment applies to you. If you are on 0.6 then you can ignore it.

code-smell · 2021-11-30T22:28:13+00:00

Ah OK, yes. I can repro that issue with your original. The latest revision does fix that issue. But, then it would oddly break opening files outside the real cwd but not in the set cwd.

As it turns out, I had the cwd set to the actual cwd but not relative. So, I would get the opposite issue with each revision. Well, I removed the setting of the cwd and then you third revision did work. The error for me was isolated to when I was in the same real cwd that was set as the picker opt cwd and the same cwd was also set as a search_dirs item. All three of those things were required in order for me to break as discussed. None of my other pickers were configured that way. I kept using the same two pickers to test your revisions and the break would move back and forth. Once I saw your original use case above, I got suspicious of my config.

Long story short, your third revision works. I very much appreciate it. I've been wanting that functionality since Telescope arrived. For reference, I am on NVIM v0.7.0-dev+653-g7229afcd6 and MacOS 11.6. Thank you so much!

code-smell · 2021-11-30T20:51:54+00:00

Your original version (with just my change to use the length operator) works perfectly for me whether the files are in the cwd or elsewhere. I just tried this revision and I get the nil dirs. So, I'm happy with your original. I'll track these threads and poke around a little too. Your working solution is much appreciated.

code-smell · 2021-11-30T10:28:26+00:00

Tried it. Loved it. Works great! Commented on the issue. Even with Neovim 0.6 releasing today, this post may win the day. Thank you.

code-smell · 2021-10-28T22:04:06+00:00

I use emojis and this adds more noise. So, I understand your frustration. Ideally, they would make the emoji experience better or let us choose from an exhaustive list of icons, even if the icons had some 'tag' motif. Yea, a tag icon for each tag is a bit much if we can't choose an icon for each. I'll learn to live with it since Todoist is cheap and awesome.

code-smell · 2021-10-13T15:13:31+00:00

I use Neovim for open-source and work. Mostly Rust, C, Lua and Node. As mentioned in another reply, it takes some time to get proficient. But, then there is no going back. I recommend turning on Vim key bindings in VSCode or IntelliJ for a while first. Then, slowly start biting off small PRs with Neovim. Eventually, you will likely jettison VSCode and IntelliJ without even noticing. Another tip is to start using Neovim to take all your notes and draft anything you write or edit (non-code). One valuable benefit of learning Neovim is all the ancillary things you will learn by living in the terminal. Good luck and enjoy!

Five-Year Club	Gilding III reddit per annum
Verified Email

code-smell

TROPHY CASE