Discussion in 'Tech Heads' started by Utumno, Nov 12, 2018.
Just starting this off as a place to solicit ideas and give advice.
Fuck tech, dig ditches. The world needs more holes.
I'm actually going to dump a bunch of thoughts/ideas here. I'm interested in what our other professional nerds have to add as well.
baby, you got yourself a stew
when anyone talks to me about manual labor or retail/sales/vocational jobs, even most assistant type work, I give a really dark paul bunyan type of example of the current place we are technologically
the individual with their amazing machine that's just simply better than the best person is coming
like.. pre Multivac area, right before it
I know very little web dev stuff, but I know how to read through HTML.
This is why I said in the other thread not to confuse people asking for basics about IT
Sanaleb was talking about being a script engineer, which is basically QA, regression testing etc
You won't do QA, and to be clear, QA in a software environment is completely different than a QA engineer in a physical production environment, obviously.
So let's talk about entry point knowledge instead of end points
Yeah, I basically fear at this point that if I lose my job, my next employment will be a greeter at Walmart if I am lucky. Currently, I am basically an admin / personal assistant.
I think entry point advice is a good way to look at this thread for starters... it's way too broad otherwise.
It's also interesting to me because I want to get at least one of my kids into tech, and I'm bouncing ideas in my brain on how to introduce them to it. Only my older kid shows any interest so far.
time to throw out the younger one
he's mentioned wanting to be a teacher. i think that would suit him well actually and i hope he means it. i don't actually think we're going to go full matrix and i do believe teachers will always be needed (next 50 years at least)
there's also some nice tech-proof trades... hairdresser, plumber, electrician immediately come to mind.
oh and art-history majors. can never have enough of those.
electrician and plumber can easily be replaced by machines, especially electrician, cabling for new buildings is usually alongside electricity, when you are building server rooms/farms you have to calculate electrical and AC costs, work with the electricians/hvac to make sure they install the right everything
i've had to go out with city electricians and explain certain things on location
there will be no vocational jobs, or so greatly reduced by efficiency from technology it won't be accessible
I wasted 9 credit hours on art history. File it under [useless knowledge with no applicable utility] taking up space in my brain next to Everquest item stats.
I'll talk mostly about web design/dev here because it's what I know. That said, I think you have to go with what calls to you if you want to keep your motivation high enough to pursue it. I did a Cisco cert for networking while I was working full-time and I damn near quit because I fucking hated it (my brother-in-law loves that shit tho). On the flip side of the coin, I found it effortless to learn SQL wasting entire weekends messing with EQEmu databases/code. I think it's important to frame new material in a way that interests you when you're pushing yourself to learn something on top of full-time work. That's not going to be easy so make it easier on yourself any way you can.
Anyhow, for graphic design I actually got my feet wet thanks to photoshopping dumb shit on this board. Most logos are just basic shapes and type arranged in an original way. Technically speaking, the barrier to entry is low.
W3 (https://www.w3schools.com/html/html_responsive.asp) is the best resource for learning html/css/etc. Click "try it yourself" on anything and you can mess with the code in real-time. You can see there's not all that much that goes on under the hood for visually-striking websites that non-IT people think look like magical hot shit created by a wizard.
You can write/edit code in something as basic as Notepad, but I always used this: https://notepad-plus-plus.org/download/v7.6.html. Code can be tested locally (make a folder on your computer and save your html/css/image files there) by opening it in your browser.
This is a decent stripped-down look into graphic design process:
You're just manipulating shapes/type to evoke a feeling. Using TZT as a example, my first thought is always establishing some general description of what kind of feeling matches the identity. TZT would have to be a bit chaotic and rough, but it's also a community so I'd want to represent that visually as well. The troll is already an identifiable mark, so that would need to be integrated (and likely simplified to just a circle or two) into the logo. Maybe I do just the head kind of looming over the "TZT" letters, but visually holding them together in a sense. Typeface would need to be rough or hard-edged. I'd probably use the old lime green/dark purple color scheme or a gold/blue EQ one. Something like that could work as a starting point.
I find that less is more with the visual relationships. For the "troll holding the letters together", I would want to only imply that in a subtle/stylized way. Take it too literally and then it looks like a crappy logo for a garage band.
I'm going into too much detail and should mention that these are two different fields (designer and developer), but they often work in parallel especially with web-based work.
I've been tinkering with react lately and it's been an eye opener. It's what Facebook is built on
also, this has nothing to do with career advice, but there's decent side money in modding/repairing old hardware
Caveat to that one is that they sell slowly since its a niche market. It's still $150-175 for about an hour of work.
most people can't be bothered to do basic soldering and would rather overpay for the labor
repairing junked stuff is the next rung up
So the first thing about IT is it's not about how much you know... it's how able you are to critical think/troubleshoot quickly... are you willing to learn and do you like to figure stuff out?
The things you need to know in Desktop support:
Microsoft, know it, love it
Mac OS, know it, it's nice, it's not hard to deal with (learn the mac command prompt calls that you would use in windows)
Linux, comprehend it, it's complicated, understand the basics required in the setting you are in (you normally are not going to be doing a lot of troubleshooting on individuals with Linux computers) (learn the linux command line calls that you would use in windows)
SCCM (Microsoft's System Configuration Center Manager)
Exchange (not everyone is using aws/azure)
Jamf is used often by Mac heavy networks
all of this stuff is extremely easy, you could learn it all in a week
You can make 70k easily just knowing that stuff
like there is a job in LA that pays 40hr for watching database servers using splunk, all you need to know is basic sql syntax, if you see problems pass them over to the database engineer
that's almost 80k before taxes
all the SQL syntax I know is through googling on how to do certain things and taking notes. it's enough to keep TZT backend db running anyway lol
Separate names with a comma.