I'm a similar late-bloomer who had to work my way into a tech job the hard way. No college degree, etc. Yes, it's possible - though it's quite hard. My advice would be to ask around and isolate the first set of skills needed to get a job that you would find interesting. QA is a great place to get started and probably a faster track into engineering than Support or Sales, but get in where you fit it and survive. Oh, and go on LOTS of interviews. As many as you can. I got rejected loads of times and I got my first job in QA with 0 experience but once I had a foot in the door of the industry, I had something to build on.
1. Accept that you may never lose your stage-fright, but you may be able to turn that fear to your advantage (motivation to prepare, or improve performance style). Winston Churchill is considered one of the great orators of the 20th century, but he had such bad stage-fright that he had to run out onto the stage. Admiral Lord Nelson, the greatest naval captain since Sir Walter Raleigh suffered from chronic sea sickness. Sometimes these are things that we just work through.
2. Do it a lot and the novelty will wear off, making it easier over time. No replacement for hours behind the wheel.
3. It's not related to anxiety, but the best book on public speaking I've ever read is "Ad Herennium", attributed to Cicero, but probably not written by him. I read it as a teenager and it changed me. https://en.wikipedia.org/wiki/Rhetorica_ad_Herennium
Do our eyeballs have vanilloid receptors? Why does it irritate our eyes if the full effect comes from taste bud neurotransmitters? I think capsaicin must be doing some other work as an irritant beyond the specific receptor.
TRPV1 is the receptor that mediates irritation. It's not actually a taste receptor. It's expressed all over the place, probably the eyes too. The fact it's also in the mouth and associated with spicy food leads to the common misconception that it's a taste receptor.
I do test automation in Javascript (Cypress) as part of the QA team at a small (less than 100-person) startup solving a real problem and making revenue from customers. I like it a lot compared to other roles I've worked in tech (sales, manual QA, large companies, agencies). YMMV.
An overview of what a typical software team looks like, and some sort of role rotation so young people get a taste of all the jobs that come together to create software. Obviously CS students should remain focused on the "Dev" angle, but understanding how QA, Product, design, sales, marketing, and management all come together would be helpful for a lot of people. Not all teams have all these roles, but the majority of engineers who work in corporate America will end up working on pretty standardized cross-functional squads for decades to come. It would be nice to have recent grads respond to that environment with something other than a sneer towards the "non-technical" folks.
I wonder if this could be done as a collab with another class, because I agree with this: "It would be nice to have recent grads respond to that environment with something other than a sneer towards the "non-technical" folks" and I've also seen something similar from business/creative/sales types that assume the engineers are just 'needlessly pedantic' because they fundamentally don't understand how computers work and that they have limitations.
Not sure how valid my case is, but in March Namecheap gave me (and thousands other Russian-based clients) a week to migrate before they ban me. The fact that I relocated to another country did not matter.
I transferred from GoDaddy a few years back. I got tired of the constant attempts to up-sell me for services I didn't want. I went to namecheap and have been happy with their services so far. The UI is clear and pretty easy to use. They also support MFA for added security (GoDaddy did not at that time).
I've been playing with cloudflare recently, and just realized they also do domain registration and DNS hosting. I might seriously look at switching to them depending on hassle and potential benefit. But I usually like having dedicated registrar/DNS that is uncoupled from hosting.
The problem with these kinds of comments is, most people who use godaddy probably haven't had issues with them either. If 10% of users have their domain terminated for bullshit reasons -- which would be a ridiculously unimaginably high fraction -- 90% of users would still say "I have yet to have any issues with them".
In the early days GD was run by evangelicals and they had no compunction against canceling a domain for religious reasons. It amazes me that they managed to whitewash their image be among those who should know better.
They're the registrar for MANY spammers and scammers, and provide hosting for plenty of them. They used to respond to abuse complaints; now they just drop complaints sent to their abuse address.
That doesn't make them any worse than, say, GoDaddy, but given enough time, they'll probably end up just as bad.
Just installed Brave and it seems to work even with Shields up. The site is under load so maybe try again. Are any of the other things (answer/explanation, code snippet, links) loading for you?
