-
Reminder: Do not call, text, or mention harrassing someone in real life. Do not encourage it. Do not talk about killing or using violence against anyone, or engaging in any criminal behavior. If it is not an obvious joke even when taken out of context, don't post it. Please report violators.
DMCA, complaints, and other inquiries:
[email protected]
The Quasi Interview - What would you like to know?
- Thread starter Stent
- Start date
- Forum Clout
- 118,229
Yeah don't fucking make a ticketing system lol. I know what I look for , but it depends on the company. I fucking hate windows and Microsoft so I can't give too much specific advice for that. I also work in more modern tech so everything is containerized and k8s.
But i started in more sysadmin so i can recommend some things there.
the first thing is to know a scripting language. For linux its bash but if youre doing more windows, active directory, legacy side then powershell is a good bet. Python would likely work but as I don't know windows I'm not sure why you want that over poweshell.
Next you want some infrastructure knowledge. Networking is always a good idea. Unless the role is purely just programming or frontend, then ignore this. But if you need to deal with any backend or full stack
you should have an idea of how networking works a bit at least. You'll probably have to deal with connecting to services, dns issue or vips for loadbalancers.
Then for more senior roles i advise distributed systems and scaling. Youll want to understand a bit about capacity planning and ops (Incidence response etc.) . This is your vague sre type stuff. Have a general idea of how to instrument things for alerts. Learn some buzz words like red metrics and have an idea of what sla/slo/slis are at a high level. Understand log aggregation and how to centralize and query the logs.
Newrelic has a free tier for agents. Get familiar with SaaS instrumenting.
Transparent Pricing - Start for Free
Simple, transparent pricing plans. Only pay for what you use.newrelic.com
What I'd recommend as a project is setting up some shit as a homelab. You can buy cheap used shit or hack some old stuff you have. Find the cheapest isp in your area and run a second line to fuck around with. Set up a firewall and router. I run pfsense but there's other open source or free ones. You can run it on old hardware. Buy a cheap switch.
I've mentioned my plex setup before that's a useful one but you might not want to explain how you're downloading movies and shows. If you're going to work with shared drives old servers etc. I say maybe set up an old raid array and have automated backups for your files at home.
If you have any iot devices it's a good idea to have them firewalled off anyway. So you can learn routers, firewalls, switches, vlans, subnetting. Etc.
If you'll deal with dns then register a domain and setup some free let's encrypt certs. You can then run your homelab all through dns and understand how tls and https works.
You'll want the devops portion as well then. You can start simple woth just some scripting (hence the scripting language) and then move up to ansible (there's one for windows) or start containerizing. Look up infrastructure as code and be able to speak about it a bit at least. You can get kinda crazy if you want on the devops side. Since you're working in legacy Maybe a jenkins server.
If you think you'll be working with vmsphere or something like that I think VirtualBox has some free shit. But just set up something like proxmox, it's free and its basically the same thing in a way.
Where the devops and infra as code comes in is you can learn how to store all your configurations as code encrypted somewhere. Then you can tear down and spin up and piece of the infrastructure. You can push updates etc.
This is all a lot so that's why I was trying to narrow it down. Once you have the infra then the programming part is easy. Let's say you set all this up but you want a nice frontend or need some custom logic. Then you can write some csharp and throw some shitty react frontend at it.
On the programming side I'm the weakest but the best thing to know is to understand the debugger for your language. Know how to lint. And google idiomatic paradigms for csharp.
Obviously you wouldn't be setting all this up. Maybe take one or two pieces i mentioned. I don't even have all this in my homelab. A fileserver was the first thing I thought of. But you can just set up another network for you iot devices. Or something simple.
I'd recommend all this because while true "full stack" is a myth with the current tech market companies are looking more at generalist then specialists now.
If you can at least understand this and contribute by automating legacy updates or moving cofnigs to git. Maybe creating a few ansible playbooks, powershellcscripts for dns updates etc. You'll be much more valuable.
Or sumtpin tssss
: Where we at wit da java? I like mine wit a lil bit of melk. sniff
G
guest
Guest
Okay, I knew the ticketing system was a dumb idea lol. I am so fucking sick of youtube faggots .
The team I want to apply for is starting to use docker, so I better get used to containers and stuff, which I've never done before.
Yes, this is great, they do a lot of backend and full stack. I'll focus on this and bring it up in my interview and how my elite knowledge of networks will be good for them.
Thank you
Halfway there, bought a switch and a server but haven't done much fucking around with it, wasn't sure what to really do. Okay, will do.
Faaawk, this is all so good. Great ideas. Thank you.
Awesome, thanks a lot.
Will do! Fawk yeah.
Yeah sql appears a lot in my current role. I'll get good at it, and find out how much they use it in the role I'm going for and bring it up.
Good admin
- Forum Clout
- 78,165
If you're just starting with docker look into docker compose. It will lmake your life much easier. I do mostly helm with k8s now but for local dev docker compose is still basically the gold standard and will give you a good enough grasp of env vars and other basic docker configuration.
- Forum Clout
- 78,165
I won't really say too much at this point as to not doxx myself too much. but what I would recommend in general non technically is to find the aspect you actually like doing. Some people hate vague requirements. They need process and structure. They get frustrated when shit doesnt work. They are a perfectionist and want to iron out every bug. Work for a big mature company.
If you want low stress easy hours, who gives a shit requirements. Work in the public sector. State universities, Healthcare companies. There's so much bureaucracy you barely have to work ever. You'll be waiting on approvals all the tiem.vif that doesn't bore you then that would be the job.
Do you like to hack things together to just et it working, jump from project to project. Shift priorities daily. If working on something for months that gets abandoned and never to production doesn't bother you then early stage startup is for you.
late stage startup is kind of a happy medium, you don't get greenfield like series a , bit you don't have 40 years of process like Microsoft would.
There's more but you get the idea. The other thing is the job itself. Do you like perfecting small changes, having you work be customer facing, more on product changes etc. Work on the front end or work in product.
Like working with customers but hate sales? Work customer success. Lile support. Work In operations. Like building shit and upgrades don't annoy you ? Work platform. Like programming but you suck at it and also like building tools and scripts, work devops.
Do you like tinkering, tuning, scaling and capacity planning. As well as monitoring and tooling , go for sre.
- Forum Clout
- 16,163
How much does he bench, and how many miles does he run?
G
guest
Guest
Four naan, Jeremy? Four? That's insane.
G
guest
Guest
- Forum Clout
- 31,104
How important is the liquor
- Forum Clout
- 98,150
I would ask him:
- Did he first hate Pat and Jackie with a white hot burning fury and has it has morphed into an icy, calculated demeanor? Or is it still white hot? Is it fun handing Pat all these Ls now?
- Will he ever rejoin the forum after the cases are over and post the juicy behind-the-scenes stuff?
- Does he think we're still hilarious?
- Did he first hate Pat and Jackie with a white hot burning fury and has it has morphed into an icy, calculated demeanor? Or is it still white hot? Is it fun handing Pat all these Ls now?
- Will he ever rejoin the forum after the cases are over and post the juicy behind-the-scenes stuff?
- Does he think we're still hilarious?
- Forum Clout
- 50,924
Check out this forum optimising query I wrote:
DELETE FROM xf_user WHERE username = ‘bendovid’;
I’d ask quasi what he’d do differently legally speaking if he had the chance to do over starting from the first case.
- Forum Clout
- 110,304
Do you find it hilarious people actually use nanaimg for non forum uploads?
- Forum Clout
- 8,697
This cannot be emphasized enough. Also, have a vague idea of the infrastructure that whatever it is that is being developed will be deployed to. Because it's not going to production with all tiers residing on a single dev workstation.
Also, some basic-level security knowledge is very helpful. I obviously don't know what sector this is in, but there's always some data that is going to need protection in transit and at-rest, and there's going to be someone else who needs to answer to management/clients/auditors re: that.
- Forum Clout
- 6,093
Does Qausi think Pat would be dumb enough to sue him again or do you expect the whole thing to end when he pays the last of the money owed?
- Forum Clout
- 31,798
The answer is Yes regardless of how you finish the question.
There's been some stunning and insightful (Dan, reference) questions. Now nobody will be disappointed and complain after the interview. That's how you executive produce!
- Forum Clout
- 16,429
I may or may not be quasi (I report, you decide) but he is definitely dumb enough to try again. He still thinks he just lost on a technicality and needs more money for lawyers to push his personal whims into law.