My last round of interview all stemmed from posting on the Who Wants to be Hired thread. I examined a few months of previous posts and looked for descriptions people had written that stood out and looked good. I went back and looked at a previous month I had posted and noticed that post by me didn't stand out. I added a well written prompt about what I was looking in an organization and a role and I feel like that helped to give color to who I was compared to a giant list of technologies I'm capable of working with.
I also received feedback from people who reached out that they went and read my personal website / blog; that gave them better insight into who I was. Don't underestimate the fact that soft skills and communication go a long way in the interview process and software engineering as a whole. Having a blog, which demonstrates the ability the communicate over a written medium, I feel is a great way help yourself stand out. It isn't a requirement to land a job, but I think it helps.
> I've fully focussed on the second approach. As a consequence, each article takes a lot of time to complete, so I generally don't finish more than one per month.
This is what I've been running into. My approach comes out of writing a bunch of code or re-writing the same sort of code across multiple projects and realizing it would be useful to share. Next I'll dump all the code into a blog post and have to start formulating what the structure of the post will be. What content do I need to add to support my claims that this code is correct (or correct enough to use)? Add in time to research alternative approaches to the code, research and write about the alternatives.
I've found that I'm proud of my finished articles but it takes awhile to get them written. I'm in the midst of one that I've kind of hit a writers block on because I have a fair bit of research left to do. I haven't been motivated to do the research and write up the findings. However, I feel like thats normal and I'll get back to it at some point.
"For Ractors to be viable to run a full-on application in, Ruby would need to provide at least a few basic data structures that would be shareable across ractors, so that we can implement useful constructs like connection pools.
Perhaps some Ractor::Queue, maybe even some Ractor::ConcurrentMap, and more importantly, C extensions would need to be able to make their types movable."
Which we see in Mike's library he has started work on a Queue and a Map.
I haven't fully wrapped my head around all the nuances to using Ractors nor have I tried to do anything with them yet. But its encouraging to see the discussion around them ramping up
Full-stack is an overloaded term, but it used to mean "a completr solution for building a web app."
From the comment above: Next.js is the opposite of a "batteries included" framework. No abstractions for ORM, background jobs, sending emails, managing attachments, web socket communication - all very basic stuff when dealing with a production application.
Well, if you went so far as to reimplement Next.js, I don't think you're using Rails either.
And frankly I'd like to see it since that's a really hard problem to just roll your own solution. And probably a huge waste of time if you're trying to ship a real product on top of it.
Combination of giving back and trying to give insight into myself as an engineer.
On giving back - Throughout my career I've read tons of blog posts that have given me the information I needed to get started or un-stuck on a task. I hope when I write about things that someone out there may wonder 'how do I X?' and my blog post shows up when googling.
On giving insight into myself - I've had people reach out while I was doing a job search that said they looked over my blog posts and that gave them a positive signal which led them to reach out to me for a position.
I think "vanilla" terminal users such as myself (e.g. I don't do a bunch of screen/tmuxing, I don't code in terminals etc) probably are not the target audience.
I've had zero issues with standard macos terminal ( once I realized how to speed up key repeat in system settings that is), so I assume I don't need this.
Same club here. I feel comfortable even with the crappiest terminal out there, as far as it allows me to write commands and read/copy output. Even the terminal in the Inferno OS felt good enough for me, like 20 years ago.
Makes a lot of sense, I fall into the same bucket as you so thank you for the response. I use the terminal to start up services and issue git commands. Beyond that, not too much.
Like psychoslave suggested, try out mise (https://github.com/jdx/mise). I used asdf for years, did the switch to mise and have never looked back for package management. It supports a huge number of languages and is performant.
I used to use ruby a lot - mostly just because it's the nicest language for scripting things on unix. I can remember trying to get it set up a year or so ago and finding the process difficult (think I was using rvm).
probably good idea to point people here before they install ruby, since it'll compile for minutes then tell you it's missing a dependency, and you have to start the whole process over.
I also received feedback from people who reached out that they went and read my personal website / blog; that gave them better insight into who I was. Don't underestimate the fact that soft skills and communication go a long way in the interview process and software engineering as a whole. Having a blog, which demonstrates the ability the communicate over a written medium, I feel is a great way help yourself stand out. It isn't a requirement to land a job, but I think it helps.
reply