It's not for me. I can see the appeal of these shortcuts, but I can see it being a wtf down the road once I've forgotten that I have them in place.
Also with something like auto-correct, you have a visual affordance that alerts you to the change (with the option to override), which just happened when I misspelled 'forgotten' above. The shell doesn't have that so something just happens without any actual correction or indication the user may have made an error. Although I am not a 'fish' user, this is something that I think it does well.
I was interested in the claim that it is warm-blooded (based on your quote). I went to the article and the link associated with the term 'warm-blooded' leads to an article that makes absolutely no mention of warm-bloodedness or thermoregulation. As such, I'm not going to put much faith in the article.
In your situation, my concerns would relate to evaluating your (1) ability to write professional software and (2) what are the gaps in your knowledge.
To address these concerns, consider contributing to an open source project.
Many of the hurdles a candidate has to clear to get a job as a software engineer are intended to determine whether you can actually program. Ignoring the effectiveness of these hurdles, the point is that you need to demonstrate the claims on your resume/CV. If you contribute to an open source project you are putting your work out there for everyone to see, including how you actually work with other engineers and how you deal with critical feedback about your work.
There is a lot of software engineering that is not interesting or attention getting but it has to be done. Often, this involves learning about things that you would not have bothered with if you are a hobbyist. By contributing to a successful open source project, you will be exposed to ideas that you might not otherwise have encountered.
House of Design | Software Engineer | REMOTE or Nampa, ID | Full-time
The House of Design creates innovative solutions for construction automation, and our software plays a critical role in achieving that. The Applications team is responsible for the software that is the hub of communication among the robots, controllers, and users. Primarily, we are looking for professional software engineers with front-end experience, though more importantly, we are looking for people that will complement the strengths of our existing team rather than fulfilling specific requirements. We want people who take pride in their work and strive to constantly improve. Our teams are highly collaborative, and you will often find yourself working with people from across the company and throughout the world.
House of Design | Linux Software Engineer | REMOTE (within US) | Full Time
House of Design create automation systems for truss creation in the housing industry. I'm currently looking to bring on someone to own the definition and maintenance of our product Linux distribution.
This role would be ideal for someone with experience using Yocto/OpenEmbedded/Bitbake. You will also need to be fluent with python, bash, and git. Some experience with AWS , Bitbucket automation, distribution maintenance, or open-source development, would be a plus.
This is a remote role, although the company is based in Nampa, ID. If you want to work onsite, that works too. Your choice.
I like it. I thought it was pretty calm and reasonable. Maybe some things could be worded a little better, but I'm not sure why there are so many strong, negative reactions about it.
"You want to work at a company on a strong growth trajectory for lots of reasons, but a big one is your own growth potential. You will learn the most the fastest at places that are growing fast, and have way more openings for promotions and leadership roles than a slower-growing company."
While I think this is a reasonable opinion, it's been my experience that companies who tout 'strong growth' are a cluster fuck. Communication quickly becomes a nightmare that is really hard to rein in. When that goes, there are a lot of likely outcomes -- none of which are good. Typically, the organization because fractured and siloed. That plucky team that punched above their weight, is now filled with a whole bunch of new people and the culture just became totally different. Now, there are a bunch of people pushing different agendas, and trying to get something done is no longer an engineering problem but also a political one.
You WILL learn a lot but, if my own experience is anything to go by, it will be lessons on how not to do things rather than "this is a good way to do things".
Being able to better communicate with one another is obviously a good thing. The point is that the language being used isn't facilitating that and that is why the autistic community has pushed back on it. So it seems to me, that it is now on the neurotypical community to listen to that feedback.
Also, autism isn't just about social quirks. These are people with different neurophysiology who experience the world in a different way. It is not simply a matter of holding a different opinion or learning a particular behavior. This is not something that can be 'normalized' by talking through it.
The autistic community is largely against gate keeping, and are quite accepting of people who are self-diagnosed. This is not about not being 'properly' autistic, but about having a voice. Being a part of society for the person you are. To not having the challenges you face in a world defined by and for neurotypical people being trivialized.
The reason that some autistic people get upset by that usage is that is diminishes how they experience life. It's like saying, 'everyone is a little black'. There is a big differences between having the genes of a black ancestor in your family tree, and experiencing life as a black person. So, to autistic people, you are not communicating the right thing.