4 ms·

Thanks. Although I do well in school, I've also never had any issues with self-directed learning and would probably prefer to go that route if possible. I suppo

Thanks. Although I do well in school, I've also never had any issues with self-directed learning and would probably prefer to go that route if possible. I suppose part of what I'm worried about is that I won't be able to see where the gaps are in my knowledge, and that I won't know when I've learned "enough" to realistically get employed. For example, I know enough to create some solid Wordpress templates. I even created an online booking system for an RV rental company. But I suspect my rental system (no longer used) had some pretty big security holes, and I would often get lost if I had to modify code in existing plugins/templates made by others. So I'm sure I've got a fair bit to learn before I'd be able to contribute well in a team setting. And of course I get worried that it will be difficult to demonstrate to a potential employer that I have the skills they want without a formal degree/certification. But I suppose that's where something like github profile is especially valuable?

FemmeAndroid 5y ago
If you end up building anything that has an online frontend, and you'd like some feedback on security or infrastructure, I'd be happy to give it a thorough look over. Send me a message at femme@femmeandroid.com. A GitHub profile is definitely valuable, but also just being able to describe what you've built and how it works can also be a huge help in interviews. Ask questions, try things, and be curious. There are also some really good books out there. It depends on what you want to do, but since it sounds like you're able to be pretty self directed, just skimming a number of software development and design books can really help you go from having a lot of thinks that you don't even know exist, or what they're called to at least building out a framework of what exists in the industry. Also, watching talks and listening to podcasts can be a nice break from the reading and the programming. They can give you bite sized insights into wildly different parts of software development. If you're planning on doing tech interviews, you're going to end up talking to developers, and when I was going through that the first time, I initially found that transferring my development knowledge from a thing I read about and practiced in isolation to a thing I could talk about was difficult. I'm always working on improving my communications skills, but I do think listening to a diverse range of people discuss tech can get you more used to talking about it. If you have meetups or other ways to interact with people about development, that's going to be the best option. Also, feel free to check out some open source communities, especially if you're particularly interested in them (or the way they're built.) Good luck!
danesparza 5y ago
Your github profile (if you have lots of good personal projects that are well documented) can be very valuable at showing how you work to a potential employer. Studying the OWASP top 10 will definitely help you understand the most common security problems (mistakes?) that developers make, and some guidance on how to avoid them. I like Cloudflare's summary: https://www.cloudflare.com/learning/security/threats/owasp-top-10/ https://www.cloudflare.com/learning/security/threats/owasp-t... You'll probably be pleasantly surprised that gaps in your knowledge will start to become evident. You'll notice a pattern in job postings that talk about tech you don't know about -- that'll be a good clue. You'll also know about related tech that sounds interesting to you -- and you'll probably naturally just learn about it. Oh -- and as for not knowing if you know enough to get hired: Just start going on interviews. The software interview is an art unto itself (and you might want to check out several excellent books at that already exist on the subject). Just being good at tech won't get you a job -- you need to be good at communicating. Going on interviews with companies (and approaching them as experiments) will let you know what you need to get better at. If you get an offer, you'll know you're getting good at it. :-) (Hint: You don't ever have to accept an offer if you don't want to)

FemmeAndroid 5y ago

If you end up building anything that has an online frontend, and you'd like some feedback on security or infrastructure, I'd be happy to give it a thorough look over. Send me a message at femme@femmeandroid.com. A GitHub profile is definitely valuable, but also just being able to describe what you've built and how it works can also be a huge help in interviews. Ask questions, try things, and be curious. There are also some really good books out there. It depends on what you want to do, but since it sounds like you're able to be pretty self directed, just skimming a number of software development and design books can really help you go from having a lot of thinks that you don't even know exist, or what they're called to at least building out a framework of what exists in the industry. Also, watching talks and listening to podcasts can be a nice break from the reading and the programming. They can give you bite sized insights into wildly different parts of software development. If you're planning on doing tech interviews, you're going to end up talking to developers, and when I was going through that the first time, I initially found that transferring my development knowledge from a thing I read about and practiced in isolation to a thing I could talk about was difficult. I'm always working on improving my communications skills, but I do think listening to a diverse range of people discuss tech can get you more used to talking about it. If you have meetups or other ways to interact with people about development, that's going to be the best option. Also, feel free to check out some open source communities, especially if you're particularly interested in them (or the way they're built.) Good luck!

danesparza 5y ago

Your github profile (if you have lots of good personal projects that are well documented) can be very valuable at showing how you work to a potential employer. Studying the OWASP top 10 will definitely help you understand the most common security problems (mistakes?) that developers make, and some guidance on how to avoid them. I like Cloudflare's summary: https://www.cloudflare.com/learning/security/threats/owasp-top-10/ https://www.cloudflare.com/learning/security/threats/owasp-t... You'll probably be pleasantly surprised that gaps in your knowledge will start to become evident. You'll notice a pattern in job postings that talk about tech you don't know about -- that'll be a good clue. You'll also know about related tech that sounds interesting to you -- and you'll probably naturally just learn about it. Oh -- and as for not knowing if you know enough to get hired: Just start going on interviews. The software interview is an art unto itself (and you might want to check out several excellent books at that already exist on the subject). Just being good at tech won't get you a job -- you need to be good at communicating. Going on interviews with companies (and approaching them as experiments) will let you know what you need to get better at. If you get an offer, you'll know you're getting good at it. :-) (Hint: You don't ever have to accept an offer if you don't want to)