>you have a week to study for a big tech interview as best

>tech

What kind of tech OP you fucking retard?

Development?
Infosec?
Systems Engineering?
IT?
Desktop support?

What?! Ya tit!

>>57378996
Software Engineer/Dev 1 (Novice)

File: 1347742470454.gif (11KB, 227x224px) Image search: [Google]

11KB, 227x224px

>Be medical student with five, 3 hour exams in the next 9 days
>mfw I read about baby problems

>do your own homework dumbass-kun

>>57379027

Can someone show me the funny in this?

CTCI

>>57378961

2-3 questions from Cracking the Code Interview from each chapter.
Crush through leetcode questions in acceptance % ascending, starting at medium then to hard questions.
Write out my answers for the generic behavioral stuff.

Done.

>>57378961
>>57379005
Can you program? If yes, you will probably be hired. You may not be hired if your asking salary is too high, or if there are more qualified candidates than you and a limited number of positions. Spend this week learning what type of programming questions are going to be asked of you, and what languages [that company] uses more often.

If you cannot program, spend this week studying how to program. A week is a decent amount of time, if you have the right mentality.

>Studying for an interview
I already know all my shit

>>57379171

Uh if you can't program and somehow you've landed a tech interview at a big tech company, then you're not going to get the job regardless of how much you study in a week.

>>57379182
They might be picking up fresh grads for cheap.

>>57379171
>>57379230
Fuck off third world tripfaggot. You have no idea how the job market works in a civilized country. Are you still trying to hire a web developer for pennies a day?

>>57379171
Someone has never interviewed at big tech.

Definitely from shit country.

>>57379167
This is good advice

>>57379005
Language ?

>>57379540
Java.

>>57379171
Falcon, I normally like you, but unless you're a serious auto-didactic or a literal autist, you're not going to learn how to code on a production level in a week, especially from scratch.

>>57378961

what are the odds you would even study the thing they ask? I would just play Nintendo

>>57379600
faggot

>>57379604
I worry about this but their is so much shit to know in the interview game.

Knowing quicksort/mergesort, balancing BSTs, linkedlist tricks, plenty more.

>>57379650
>Knowing quicksort/mergesort, balancing BSTs, linkedlist tricks, plenty more.
Do they actually ask for this standard library included garbage? I'd expect them to ask relevant stuff, not "ey do you remember that class from college?"

>>57379665
Yes? I'm pretty sure they do.
It's a fucking game, rarely does the interview reflect on what the programming relevant to the team will consist of.

Not always, but definitely not rare either.

The interview game is such a meme.

>let me test you on something useless you learned in class 2nd year

Fuck that shit. Just look at the projects I've done and hire me faggot.

>>57379650

I've never been asked a sorting algorithm question on an interview before. Mind you I've only been to like 3-4.

>>57379665

I've been on the other end of the table for interviews for a very big tech company.

You won't get asked to specifically implement any algorithm or datastructure. We're not going to ask you to make randomized quicksort, or kruskal's algorithm, or fucking skip lists.

What you will get asked is thinly veiled generic data structure/algorithm question. At least a couple or a few of these.

The idea is that if you have the knowledge of all that shit listed (and plenty more) then you have more tools in your tool box to answer. Most of the algorithm/DS questions you will be asked have many ways of solving them. Some clearly better than others, and some solutions have trade offs which one might want over the other in specific situations.

Those specific kind of programming questions are generally one part of the long tech interview process.

Ideally, you will get other people on your interview loop to ask you about design, architecture, general behavioral stuff, etc.

Lastly, always remember that the goal isn't to necessarily get the right answer. We want to know how you think and how you approach problems. Also really good interviewers will always be able to raise the stakes and expand the breadth or depth of any programming question. Not only do we want to see how you think and approach problems, we want to see how you deal with ambiguity, stress, and what you do when you genuinely have no idea what to do next. Do you give up? Do you panic? etc.

>>57379690
> Just look at the projects I've done and hire me faggot.
This is great but Pajeet's have ruined the industry so much by lying on resume and portfolios that big tech now has to test this kind of bullshit to filter them out.

Acid wash tests take care of them pretty quick.

>>57379711
Any tips my good anon?

Anything at all, i'm sure you've observed many common slip-ups.
Things like making sure to clarify at the beginning what they mean, or always talking out loud. Etc.

>>57379711
Yeah I assume that would be more the style.

File: 1383052494760.png (49KB, 172x159px) Image search: [Google]

49KB, 172x159px

>had my first interview with a software company
>4 interviewers
>every question was technical
>mfw

Never been more nervous in my life

>>57379910
What questions did they ask, if you can remember?

>>57379910
I went through palantir and I had 1 screen, 4 onsite, then 1 after.

>>57379916
How to poo in the loo.

>>57379268
>Are you still trying to hire a web developer for pennies a day?
I am offering a middle-class salary, and it is more than the typical rate that other people are offering here. No, I cannot offer a first-world salary, because I cannot afford to pay that much, and I am not living in the first world.

>>57379600
OP did mention it was a novice position. That said, you are probably right.

>>57379916
I am interviewing a guy in the next 15 minutes. Want to see the programming questions I am going to ask?

>>57379951
Can you interview me for practice? Would be kind of you.

If you can't, just list the questions.

You can't learn the answer to every programming problem in a week.
From my experience interviewing people, here's the advice I'd give:
*Ask clarifying questions.
*Learn how to write code on a whiteboard (if that's the interview style)
*Get a working understandable solution first, then discuss performance if there is time. *Never work yourself into a corner where you don't know what your own code is doing.
*Speak aloud what's going though your mind (important, the interview should never be silent for more than 20 or so seconds)

When I was interviewed for a small company for an entry level job, I was asked to do:
fizzbuzz
fibonacci
linked list
A word problem

When I interviewed at a big company for a 6 figure job, I was asked to do:
Finding a missing number in a list of numbers in a range.
string to floating point num.
Odd 2 dimensional binary search tree.
Convert a depth first tree's nodes in a breath first order.
In a directed cyclic graph (not a DAG) with a single sink, find the sink.

Good luck

watch anime

>>57379983
I would love to interview you, but you may need to wait something like an hour or so, as I am literally waiting for someone to come in for an interview in the next few minutes.

Send me your resume. I can call you via Google hangouts, if you that is convenient. My email is public.

>>57380006
Sent to what I think your email is.
Can you reply and confirm?

>>57380041
Did not get anything yet. I am going to afk for the interview, will check my email once it is over.

>>57379827

If you're getting interviews, then I wouldn't worry too much about personal projects.

If you're failing interviews, then you have to be aware of what you might be doing wrong.

If you're in school, I would get a friend to interview you and then have them provide feedback. Preferably someone who has had an internship at a big tech company or a reputable start up.

When it comes to the programming questions, generally people fail with the following

1. Not explaining their approach beforehand
2. Not explaining while they are coding
3. Very sloppy coding
4. Brazen fixes instead of being thought out
5. Not properly testing
6. Not clarifying requirements
7. Straight up just giving up.

CTCI covers most of that. In the end, a lot of it is just practice. It sucks but just put the time into it. No one on this earth is going to give you pity for not wanting to play the game, when the prize is a cushy 6 figure job.

For behavioral questions, prepare before hand and practice! Write out every story you have for all the diferent likely questions.

I've noticed in interviews candidates tend to think of one story and then use that to answer every question. It might work from the candidate's perspective, but its better when the answers to these questions all stem from different places. Usually I attribute this to a candidate just being nervous.

Practice anon. Practice. Practice alone in front of a whiteboard, with pets, with peers, etc. You have to be confident, but not a cunt.

>>57380065
Sent. Pls help. If you didn't get just give me a hint to where it is.

>>57379951

OP didn't mention it was for a novice position. You don't even have the proper reading comprehension to understand the basic scenario that OP posited.

No big tech company (Msoft, Google, FB, Amazon, etc) is going to hire new grads for cheap. Do you have any fucking clue how expensive hiring the WRONG person is?

Fuckers have to get trained, and other developers have to spend time helping them with all their shit for at least 3-4 months before they can be somewhat useful. Having some idiot produce shit code is expensive.

And yes, those companies are desperate for hires. The key is that they are desperate for GOOD engineers, not bottom of the barrel shit. New grads at those companies make over 6 figures. No one is going to hire some fucking idiot who has just learned to code in the past week.

If you're browsing this thread I would advise you not follow any advice this fucking idiot has.

>>57380118
I have a really impressive project that I hope to carry as my crutch. It has so far worked.

I can talk about a lot of interesting shit, but i'm definitely mediocre in problem solving.
I think i'll just have to get lucky. Still going over every problem in CTCI.

I'll do anything it takes. I'm just behind because I didn't really want to interview yet but was lured, and couldn't delay it.

>>57379985
>Learn how to write code on a whiteboard (if that's the interview style)
>Tfw your writing is illegible, your sentences slant down, your character size varies, and you can't properly close a circle ever
Suffering

>>57380154
Seriously it doesn't need to be pretty, just readable. Write bigger, Slant upwards to counteract, practice writing letters. I had a shitty handwriting, and that last one made me feel like a fool who needed to go back to first grade. However, after filling sheets of paper with the same letter written over and over again, my handwriting turn from shitty chicken scratch to typewriter perfect.

>>57379951
>I am offering a salary
Hire me?

Brush up on general programming and algorithms. I'm pretty good at talking about my own projects and other bullshit so I don't worry about that.

In general I don't cram for interviews because I can't memorize a whole bunch of new algorithms in a week and it just stresses me out. I focus on revising what I already know and if they throw something at me I don't know, I do my best and admit I'm not familiar with the problem.

>>57380214
He's offering literally pennies a day. Anyone in a third world shithole could make more doing shit on Mechanical Turk.

>>57380214
If you are a Malaysian, or with a Malaysian PR, I can interview you.

>>57380224
>Anyone in the third world could make more on Mechanical Turk.
I am giving above average salaries. Not HUGELY above average, but above average. They would have to go for a much larger company with a much larger budget, or go to another country altogether, if they wanted to get paid more.

But still a third world salary. I cannot do anything about that part.

File: 1441066663479.jpg (234KB, 853x1280px) Image search: [Google]

234KB, 853x1280px

>>57381134
Sounds decent, anon. Dont let these western neckbeards get you down.

>3 hours later
>no interview questions
fuck off falcon,this isn't a government secret

>>57381301
I am interviewing the OP live right now.

Probably read a book like Cracking the Code Interview

>>57379556
I study how to poo in loo

So I took falcon's interview, am OP.

The questions were not difficult, but definitely a good few levels above fizzbuzz aside from first 1,2.
Difficulty is a 4/10 I would say compared to other mock interviews i've had and seen.

Syntax is what really fucked me, am pretty new to Java so I had some minor slip-ups here and there. Especially because i'm tired as fuck.

Feedback is great, but admittedly the behavioral questions were quite non-American as far as the answers he expected. Not his fault of course.

Also like how he furthers the constraints to see thinking on the fly. Good stuff.
Overall great mock interview, props to him.

>>57378961
I'll just check how to reverse a binary tree and go to sleep.

File: Untitled.png (49KB, 639x575px) Image search: [Google]

49KB, 639x575px

>>57381308
Interview over. I asked OP most of the code questions in pic. These are trivial for a senior programmer, so do not get upset: OP is looking for a novice position, and I have been interviewing junior developers. If you are looking for questions that are asked in senior interviews, then other people may help.

The theory questions are stuff that I got from previous threads in /g/, and online. I have never asked them in an interview... yet.

Enjoy.

>>57380188
coding on whiteboard is worst fear. what if you forget to add lines before and stuff? I guess strategy is to use a lot of space in between lines just in case.

>>57381623
Theory 4:
I don't suppose pulling a time signal off of a gps satellite is allowed so the time can just be sent over the packet more than 3 seconds before it's time. How syncrhonised is synchronised? GPS can get you within a nS or so. WIth a long enough time to get a feel for the link, ntp can get you within a few ms with pretty good certainty.
5: lol. How to weed out Richard Stallman: the interview question.
>>57381723
I don't understand testing a programming language in an environment without a compiler. That's what pseudo code is for. I had a CS professor who made us write c++ on a test. I always got at least 10% of the value of the question taken off for some stupid syntax error. I turned in my 500 line homework assignment and it worked 100%, why do you need to test my ability to make machine readable code? Compiling a single file is not an expensive process. Not doing it is like buying word processing software and not using the spell check.

Installing gentoo and reading sicp.

>>57381623
I'm not a programmer by any stretch of the imagination, but a few of these seem obvious while the rest I'm probably just too dumb to grasp.
code 1: echo $firstName $lastName
code 4: nested for() loops that increment x and y then multiply them
theory 1: gut says TTH, but I'm thinking either is equally random
theory 2: set 2 aside, weigh 3v3. if scales are even, the heavy one is in the two set aside. if scales tip, set one aside and weigh remaining two. same thing.
theory 3: start from floor 50 and test drop. if it breaks, go to 25. if not, go to 75. repeat by cutting gap in half each time.
>pretty sure this isn't right, because if it breaks actually breaks at 5 and your first two tests are at 50, then 25, at best you know it breaks at 25 or under. this isn't accurate enough imo but only allows for two eggs.

would love to hear the answers to these questions but totally understand you not posting them considering they're meant for an interview.

>>57381623
Wew
I guess programming just ain't for me

>>57382260
>gentoo

>>57382802
>not maining Gentoo

>>>/r/eddit

>>57382807
>not running debian in a VM

we got a special snowflake here.

>>57379175
no you don't

>>57382533
Code 1-5 are easy enough that anyone who paid attention in class can get them. 6 is the one that will show whether the candidate is a programmer or a copy/pasting "coder". Perfect syntax is not critical, but working logic is.

You can find the answers for most of the theory question online. Just make sure that you think about them enough to exercise your brains properly. If you just give up and get the answers, then you are robbing yourself of an opportunity to honestly test yourself.

File: 1469135112817.png (237KB, 347x427px) Image search: [Google]

237KB, 347x427px

>>57379011
>be in cram school with thirty two 4 (four) hours exam in may, in 8 different field with no connections whatsoever, over the course of less than a month
>not counting the oral exams afterwards
>my face when I read about little baby's problem

Just bought a fucking whiteboard to practice this cuck shit.

how do i not get tired from studying this all day

>study for interview

>>57383746
how else to prepare for 8 hour interview

>>57383795
They (e.g. Google) usually ask CS101 algorithms questions do you should be able to figure those out

Snort some meth to improve your self-confidence

>>57383818
Questions i'm seeing on glassdoor are definitely not CS101 questions. Have you interviewed with them or just pulling shit out of ass?

If they were just CS101 then you would see a good chunk of CS majors being google-ready, which obviously is not the case.

Having gone through multiple interview stages with companies like Uber(easiest), Facebook(medium) and Google(hardest). leetcode.com is your best bet, it's seriously worth just going through and solving from easiest to hardest. Every questions I've been asked has been there.

If you're going for a general software engineering role (or mobile in my case) they generally don't ask the 'hard' algorithm questions as there really just isn't enough time and they tend to be looking for your understanding of basic data structures and your thought process when you are given a problem (Do not underestimate how important this is). Due to this memorizing answers rarely works because it becomes quite obvious if you're pretending to solve a problem you already know the optimal answer to.
For this reason, what you should really be looking for is patterns in how particular problems can/should be solved and the correct data structures to use in the solution.

They potentially may throw you some general array based sorting problems but the smart thing is to focus on problems based around: LinkedLists, HashMaps and Binary trees. In that order.
It's also a good idea to practice both Iterative and recursive based solutions as some interviewers may ask you why you chose a particular approach or if you can implement both.

Be aware the faster you solve a particular issue (or they feel you didn't tell them you already know the solution), the more they're going to grill you on your implementation and why you made specific choices. They may even add extra parameters to the original question to complicate it.

Also if they've scouted you and you're going through their in-house recruiters, pay careful attention to what your recruiters tells you to do for prep, they're telling you for a reason and in one of my cases they gave me 3 example type questions they asked me 2 of them in the later stage interview. Remember, they better you perform, the better they look.

Good luck.

>>57384284
So should I memorize sorting algos or not?
If so, probably quicksort would be enough. yeah?

>>57381623
Code 5:
One array containing all card types (ace to jack)
One array containing card types (spades, clubs)

choose random from first array min being 0, max being array size
choose random from second array, min being 0, max being array size.

concatenate values from method call to be one card.

do method call again and display the other card.

Of course I didn't think of removing the card because the data structure doesn't support it, maybe just have a list of 52 cards.

File: fuck.png (149KB, 1534x204px) Image search: [Google]

149KB, 1534x204px

This one is the end of me.

>>57381623
Code question 6:
Create a boolean array with the size of 1000.

Loop through array of integers
Set each Boolean index to true on each integer
If Boolean index was already set to true, break loop

Could also implement this using a hash set

>>57384531
Isn't hashset essentially the same as your first solution?
Can't you think of inserting the boolean in the i index for the number as a hash-table because the function is instant and no collisions?

any advantage to either?

>>57384693
bump because I really want to know if there is any difference.

>>57384693
>>57385073
With a hash set (of type integer) it reserves a portion of memory so that you can add integers to the set. Calling a contains method goes through a hash function to see whether the item exists in the hash set.

With a Boolean array you're specifying how large the portion of memory you're using, everything is initialised as false. You also can call each of the indexes of the array unlike a hash set. A hash set is great for searching items in the set but difficult to get all items in the set.

>>57385187
this is confusing me, but does this mean the boolean array method is better? instant search and get, yeah?

hashtable has to go through a hashfunction and potential collisions. so it's strictly worse in this instance?

>>57385187
The larger the Boolean array, the less efficient it becomes due to memory allocating space for pointers. The worse the hash function, the more collisions there are (running up to O(n))

With this example it's likely that a Boolean array would be faster, but don't take my word for it, try testing it out.

>>57385323
Interesting. thanks anon.

Would having more memory for pointers in the Boolean array somehow slow down the function?
Does occupying more memory affect speed? Or is it independent of speed in that instance.

I should just time this shit out I guess.

>>57385252
>>57385323
Also to add: for Boolean arrays this is implying that you know the maximum number, as the maximum number is what determines the size of your Boolean array


HashSet<int>

For loop:
If set.contains(number) break
set.add(number)


HashTable<int, bool>

For loop:
if set.containsKey(number)
If set[number] break //optional
Set.add(number, true)

Boolean array[1000]

For loop:
If arr[number] break
arr[number] = true

For loops:

>>57384531
why wouldn't you just make a loop that checks each index of the original array and return the current index if array[i-1] == array[i]. seems a lot simpler

>>57383135
And yet you still find time to shitpost?
You're going to fail you degenerate

>>57385558
c++ example
for(int i = 1; i < array.length(); ++i){
if(array[i] == array[i-1])return i;
}

>>57385599
or just start at index 0 and check for index i == i + 1, returning i + 1

>>57385599
this means the duplicate elements are right next to each other, problem talked about unsorted.

won't work.

>>57385449
Yes to be exact:

For a 32-bit Boolean array (up to index of 4M), eachindexis 4 byte integer and also 1 byte for reference to the bool array object, that makes 4 * 1000 + 1 = 4001 bytes

Depending how much memory the HashTable or HashSet takes it may be more or less. This is mostly handled by the library itself though.

>>57385558
Because that assumes that the duplicate is next to each other and not somewhere else.

Take for example {3, 7, 4, 2, 7}

>>57385619
>>57385624
true. misread the question

>>57385624
Whoops, miscalculation. It should be 1 * 1000 + 4 = 1004 bytes for a Boolean array of size 1000

>>57385636
int[] occurences = new int[array.size()];

for(int i = 0; i < array.size(); ++i){
++occurences[array[i]];
if(occurences[i] > 1)return i;
}

>>57385664
>>57385624
Still trying to understand how using more memory affects speed. Just want to understand exactly what is going on.

I understand that it may take more bytes, but where in the compiler or o/s will this affect speed? Doesn't saying array[n] always have the same fetch speed independent of array size? why does a bigger array take longer to fetch it?

>>57379011
Tell me about it
These CS retards don't know suffering until they've taken a test like the PCAT or MCAT

>>57379011
>be engineering student with 8 4-hours exam over 5 days
>hear about some mednigger trying to look down on others

>>57385758
Only medfags are stupid enough to become a doctor in 2016 with insane tuition, insane competitiveness, trending decrease in doctor satisfaction and well being.

And shitpost at the same time.

nah i'm kidding. Don't know how you guys do it, it must be fucking robotic. you guys have my respect if you can make it all the way through without cheating/affirmative action or shit school.

>>57385793
Stop making us engineering fags look retarded when you genuinely try to compare difficulty in med school and engineering degree.

It's laughable.

>>57385727
Because behind the new bool[1000] method, the machine is allocating a memory space for your variable to use along with creating pointers for each of the objects.
Allocating memory has a larger performance impact when you do start trying to allocate large portions of memory at once.

>>57385806
I'm a pharmfag and I agree
I'm taking a lifetimes worth of biochem just to count pills
Doesn't help that med in general is being crunched in terms of pay and jobs.
The only thing keeps me going is that there's a lot of cute autistic virgin chicks in pharm and I'm only going to have 1/4th of the debt of an internist.

>>57385877
Honestly from my standpoint, i'd guess the most depressing part of being a doctor is treating so many degenerates.
You guys basically dedicate your lives and an insane amount of effort to helping humanity, directly, when most people are fucking stupid and have no motivation or just assholes.

That's something I can't get over. I'm probably just a cynical fuck but I wonder how common it is for doctor's to have those feelings.

>>57385964
>dedicate your lives to humanity

Nigga, I'm a severe asthmatic and I can assure you that 70% of my doctors have seen me as another patient, one to diagnose and move on.

For five years of my childhood I was being passed around doctors who diagnosed a collapsed lung as pneumonia. Finally, after being hospitalized so much, one respiratory therapist who I could tell truly cared diagnosed me correctly and in three short surgeries I was fixed, like a new kid. Grew about 3 inches that year even.

Many, many doctors are simply there for a fat paycheck. I understand there's good fellows who truly care but it's few and far between.

>>57386154
what country/year did this happen?

human body is insanely fucking complicated, mistakes happen.

>>57385840
You autistic fucks already look retarded
Every single engineer i've spoken to that was under 25 coun't utter a sentence with stuttering.
Not to mention the general reddit/tumblr meme faggotry thats taken over most people in STEM

>>57386404
>Not to mention the general reddit/tumblr meme faggotry thats taken over most people in STEM
and not bio majors? Do you not know medicine is considered STEM too?

>Every single engineer i've spoken to that was under 25 coun't utter a sentence with stuttering.
Yeah you're a fucking retard. Stop embarrassing yourself.

I took the MCAT for shits and giggles during high school and got a 41. Do med students seriously spend 4 years of undergraduate study learning this crap?

>>57385850
I see. Interesting.

>>57386485
No you fucking didn't
You're telling me you memorized a years worth of biochem in high school?
Fuck off
Also they do a course check before you can even register foe the exam you fucking idiot.
>>57386470
I'm sorry your field is full of autists
Bio fags are usually premeds too preoccupied with fucking eachother over and trying to pass orgo to be meme spewing faggots. Insufferable sure, but in a different way.

File: 1434942265510.jpg (33KB, 527x497px) Image search: [Google]

33KB, 527x497px

Medfag here, I can't believe how many of you autists got so asspained over a post that took me 5 seconds to write. My test this morning went fine.

>>57383135
What the fuck is cram school?

>>57385793
>Work in a tutoring academy before matriculating to medical school
>Be top tutor for chemistry and biology, also teach Spanish and other bullshit classes
>Have neckbeard coworker with a degree in aerospace engineering or something
>Fucking embodiment of leddit
>He comes in with a fucked up shirt collar every few days
>I go up to him every time to fix it and tell him he's "such a handsome boy!" with a lobby full of students watching
>mfw I emasculated him on fairly regular basis

This is what I think you're probably like.

>>57385964
A lot of doctors have to distance themselves from human feeling while working with a high volume of patients. I've only seen a doctor cry once. Schools are trying their hardest to make students more empathetic, but there's a reason for the incredibly high suicide and substance abuse rates seen in physicians. It's a hard and thankless job that you have to sacrifice your youth for. Yeah, the paycheck is cool, but 8 years of hard education, competition and work comes first. And that's not even counting residency and continued medical education.

>>57386154
Most doctors are trained under the assumption that if one hears hoof beats; think horses not zebras. Pneumonia is more probable than a collapsed lung in any atraumatic setting. Especially in younger patients. I'm unsure of your history, but a respiratory therapist is taught to see the patient in a different light than your standard doctor. I'm sorry that happened to you, I'm glad you're better. To be honest, the materia medica is so vast that things are easy to miss. Physicians constantly check sites and textbooks while on the job to make sure they're not killing you. Hell, I'd wager that 99% of all physicians have forgotten basic biochem.

>>57386485
No you didn't.

>>57386818
Fuck pre-meds

>>57386818
I was already taught biochem in high school. Not everyone goes to a school in the ghettos.

>>57378961
I wing it and hope for the best

>>57387130
how has this worked