896 karma · joined April 17, 2010
https://www.consumerreports.org/cro/news/2009/05/update-abou...
Who are these non-technical people that you know that are not only using MFA but also know that SMS is insecure for MFA?
Rather than putting them down I'm happy they're willing to share and bring knowledge, that some communities already know, to even more people.
I definitely agree that lack of education is a disadvantage, it just means you have to start a different way. that could mean your first few years is coming in through a side door before you start getting relevant experience.
I don't think everyone should take the path I did. If you can afford it, college is a really good option and I would never discourage someone from going that path. But there are other paths, if you work hard, and have some luck.
I'm now in a position that interviews and helps make hiring decisions. I still know a lot of people from South Florida that have spread out all over the country. There are many of us who don't come from traditional backgrounds that have progressed into leadership roles where we impact hiring who do not require college.
Yes it is very competitive, yet so many companies are constantly turning people away, people with and without college degrees. I'm so happy that there are so many more resources today compared to what I had when I started. MOOCs are awesome and I use the to this day for continuing education. I've been part of apprenticeship programs to train bootcamp graduates as SREs. And I've helped mentor people internally transferring from support into SRE.
College is definitely the most typical paths but there are still paths for humble people willing to start that the bottom and work hard. College just isn't an option for everyone unfortunately.
I generally like to work with people, and at places, that value your contributions and experience rather than your credentials. I've been lucky enough to find that in every place I've worked. I can't say my experience has been one of only working with people without degrees. I've worked with amazing engineers with and without degrees and don't put much stock in the degree itself.
Thankfully for me I consider it a positive selection bias as I wouldn't want to work for a company/manager with such insular hiring criteria. Unfortunately it does make it harder for people just getting started in their career.
Going to college definitely makes things easier, and I don't advise people to take the path I did but there are paths other than college that still work well for this industry.
I got a job doing tech support for a web hosting company at 19 (requirements for getting hired included listing 3 FTP clients, listing 3 e-mail clients, what is whois, and things you could teach to anyone). I worked with many high school dropouts as well.
After getting that tech support job, learning about open source (LAMP stack) changed my life. I didn't have much money but I was able to self study on linux, apache, mysql, php/perl/python with minimal equipment. Over the years open source has provided and avenue that allowed me to better myself to the point I've worked as an SRE for Google/YouTube, a Staff SRE for Dropbox, and starting soon as a Staff SWE at Discord. Open source has given me so many opportunities, made me a better person, and allowed me to provide for my family.
There are a lot of people like me in the industry who care about socioeconomic diversity. I will absolutely interview and hire dropouts if they are driven and capable.
function e() {
echo $#
}
$ x="hello world"
$ e $x
2
$ e "$x"
1 flock -xn /path/to/lock -c /path/to/commandNo need to use the past tense. Reason 10 just came out 2 days ago and added some awesome new synths!
https://github.com/dastergon/awesome-sre
If you're looking for a community of people to interact with I've found the following Slack teams to be very active with lots of helpful people:
Take a look at SliceTricks[0]. These are all pretty simple operations in other languages that the Go authors think users should be forced to write manually so they understand the costs. Reading these in code reviews is definitely not a breath of fresh air.
I also see Go users develop bad habits that will burn them in other languages, like returning a reference to a "stack" allocated variable. In the same vein, if you care about performance you have to internalize the escape analysis rules, which most new users won't know about.
There are tons of footguns[1] in Golang as well. I constantly see people get burned by issues at runtime. I truly believe that the Golang benefits are short-sighted. You get some upfront development gains that you end up pain for with less reliable software. I personally would rather pain that cost upfront where possible with the compiler telling me when something is wrong.
[0] https://github.com/golang/go/wiki/SliceTricks [1] http://devs.cloudimmunity.com/gotchas-and-common-mistakes-in...
For me, safety is the killer feature in Rust. It's also exciting because it brings systems level programming to a new generation of programmers without all the risk.
It should be a good summary of the event.
I only mention those two together as the previous options for low level, no runtime languages. Outside of Rust both C and C++ were independent options I've considered investing more deeply in.
I think C++ has a lot of awesome stuff coming out but I find Rust more pleasant to code in. Also having package/dependency management has been great compared to using the old versions of libraries that come with distros or tracking down all the transitive dependencies of software. Rust is just a more delightful experience out of the box.
> Though if you're a SysAdmin and you write your codebase in Rust.. that's some nice job security. ;)
I definitely understand this but I don't think it's true and will be less and less true over time. It is becoming very common in the SRE/SysAdmin industry that strong coding skills is a requirement. When I started 10 years ago that was very different but it's becoming harder and harder to find jobs as a Linux grunt. The SREs I work with care about software engineering best practices, code review, testing, continuous integration, etc.
Also, even if that were true, I'd much rather have people with a weaker understanding contribute to Rust where the compiler has your back. If you haven't used Rust you might be surprised how good the error messages are. Once you spend a bit of time understanding the basics the compiler is super helpful.
I'll admit that OCaml is something that I've looked at before but it didn't have the staying power for me. It's likely just because it was too different at the time compared to what I was used to.
As an SRE/SysAdmin I struggle to believe that C or C++ can be written safely. It is very common that I see software being emergency patched because of memory unsafety from very experienced engineers in ubiquitous software.
Why would I need the performance/efficiency of C in the first place? Well, I regularly write software that runs on thousands to tens of thousands of machines in production. This software runs below the service. I feel a certain sense of pride in minimizing my observer effect on the system. With Rust, compared to Python, I can write software that has more functionality with a fraction of the memory and CPU utilization.
Another thing that has become more appealing to me is the strong static type system. Not having a formal background in CS I fell in love with Python for how it enabled me to move quickly, and Python is still my go-to language for most things, but after years of supporting large production sites plus running my own code in production I'm a bit tired of runtime exceptions. We have great exception logging and there are entire classes of bugs we'd just never see with Rust's type system and error handling.
Essentially, Rust gives me new super powers and the borrow checker is my sidekick making sure I don't shoot myself in the foot.