This, plus the multiple-cursors package, can save entire minutes off tedious file-renaming operations. (That may not sound like a lot but trust me every second counts when you're just renaming files.)
On the flip side, as someone who's tried to change stacks or IDEs or other software a few times, there's something to be said for already having momentum using existing solutions. Sometimes alternatives can be a little better, but not better enough to justify the time/energy/etc costs of switching. And more often than not, alternative solutions have their own flaws too. I tried three times in the past week to switch my portfolio website (https://sdegutis.com) to using Jekyll or Metalsmith or Hexo, and each time it just didn't prove any better than my own hand-rolled Node.js site generator, and in most cases, it was definitely worse in some ways, at least for the specific requirements I had. So switching tools can be good, if it's legitimately better in some way, and not worse in any other ways. But that doesn't isn't the case as often as we'd like to hope.
That's my same experience with programming. That's kind of what I was getting at in this article actually: that you get better by doing your best and making mistakes. Nothing beats hard-earned experience.
Good point. You're right that passion helped me to gain the experience I have now. But at this point I can't lean on that same passion, I had to find another motivation. I wonder how many people hit this same point and just let themselves fully burn-out instead.
Meh, joke sites like this aren't nearly as prominent as sites for apps, I'd really like a .app TLD instead. That said, the distinction between app and service is blurring a lot, so Spotify and VS Code probably both qualify for .app but one also has a web interface. Everything is confusing, let's just stick to .com
In the same way, I use VS Code mostly now (for node stuff) but I still load up Emacs and use Magit whenever I need to do serious version control, meaning basically anything more than just "glance at the changes and commit everything."
In my experience having switched from using one IDE to another a few times, the difficulty for me is usually that both IDEs do 90% of what I need perfectly (after a few days of tweaking), but the other 10% feels is missing and feels critical, and in particular, neither have the same 10% missing. So I kind of have to ask myself, "which critical features am I okay with giving up?" and I can't decide so I just stick with what I know and have muscle-memory for.
I'm not that optimistic. In my experience, nightmare-level code will be written by the person who wrote it no matter what language they use. Rust doesn't look all that cleaner than C++, just that it has a few more safety guarantees. I'm sure terrible code will be written in it. And I'm sure clean code will be written in it that people without context will call terrible code.
Can confirm. I worked a pretty decent software job with lower pay than others make for the same job for the past 5 years. Could barely afford insurance for my wife and I. We actually had to just give up and not pay for it the first few months of this year before I was laid off, figuring that paying the "fine" for not having health insurance plus whatever unlikely emergency medical costs we might have was cheaper. As soon as I'm laid off, we're on public aid and have the best insurance, and since every job I applies to rejects me, and haven't found any freelance work through sdegutis.com yet, it looks like we'll have a few more months of being able to have better health insurance than I could afford when working a decent programming job. The system is broken and literally ridiculous.
It may not necessarily be in active development, but it's a project I'm very proud of. It's a legitimate text editor built from the ground-up in Objective-C including its own parser and lexer, and the ability to read theme configuration files. I'm very happy with it and I think it stands on its own as an interesting project.
Can't agree with you here. Your comment seemed to be saying "VS Code may be better than Atom in every way, but that doesn't mean we should keep bringing that fact up, or that anyone should switch because of it." It's actually a perfect reason to do both.
> "you cannot currently use WSL to run persistent Linux services, daemons, jobs, etc. as background tasks."
Still, this has me wondering if that's the ultimate goal here. Is Microsoft trying to position Windows 10 as a high quality Linux server in the long-term?