|
KernelSlanders posted:I know what it is. It's what I downloaded all my porn torrents in circa 2001, and I used adware to open them. Are people still using this, particularly in a professional setting? If he's sending you a split rar with "pr0per" in the filename, and an NFO file with shout-outs to Razor1911 and Fairlight, then sure, judge away. If he's not, then it's just an archive format, get over it. e: if it has a sweet 64k intro, though, hire them and don't look back Space Gopher fucked around with this message at 04:49 on Mar 20, 2017 |
#
?
Mar 20, 2017 04:41
|
|
|
|
| # ? May 17, 2024 22:52 |
|
|
Vincent Valentine posted:For what it's worth, personal projects are the only reason I got my current job. I don't believe they truly cared what the app did, or much at all. Just that I had code they could see and talk to me about. That being said it's from 2015 and I wouldn't include any of my personal projects on my resume, and, like, next time I throw a personal project together over a long weekend, it'll be something that just shows "hey this dude isn't bullshitting when he says he knows LANGUAGE."
|
|
#
?
Mar 20, 2017 04:59
|
|
|
KernelSlanders posted:I know what it is. It's what I downloaded all my porn torrents in circa 2001, and I used adware to open them. Are people still using this, particularly in a professional setting? Most people are probably using 7zip or WinRar in a professional setting. I think you are the weird one here.
|
|
#
?
Mar 20, 2017 05:25
|
|
|
We use ASCII exclusively around here, boy.
|
|
#
?
Mar 20, 2017 12:07
|
|
|
In my experience, people generally use RAR because they are using WinRar as a general unzipper and it defaults to making a RAR when you use it to compress stuff.
|
|
#
?
Mar 20, 2017 12:46
|
|
|
I'm idly considering looking around for a job just to keep my options open (ever since I started making money as a developer I've been a freelancer or transitioned into the position inside a company I already worked at. This means I have never interviewed/job-searched as a dev). Currently my github is a bit of a mess with 40+ public repositories. There is a mish-mash of little scripts I wrote for someone else, things I wrote for myself, and a couple open source projects I created with 20,000+ users that I haven't actually done any work on in 8 or more years so I'm not exactly proud of their code quality. Should I clean this mess up or should I just say "here's my github page, these are my good projects".
|
|
#
?
Mar 20, 2017 15:18
|
|
|
Thermopyle posted:I'm idly considering looking around for a job just to keep my options open (ever since I started making money as a developer I've been a freelancer or transitioned into the position inside a company I already worked at. This means I have never interviewed/job-searched as a dev). I would say clean it up. It's hard for a person taking a quick look to tell what you did. I went through and removed a bunch of repos, merged a few other small ones, and wrote two sentence descriptions for each of them. Also, you can pin your 6 favorite projects on your main profile page.
|
|
#
?
Mar 20, 2017 15:56
|
|
|
You can pin repositories in GitHub, and they'll show up at the top of your page.
|
|
#
?
Mar 20, 2017 15:58
|
|
|
KernelSlanders posted:This isn't helping his cause. I agree, not hiring anyone who might be of a different family background than yourself is a good and legal way of selecting candidates
|
|
#
?
Mar 20, 2017 16:15
|
|
|
There's a local insurance company (~400 employees, 60 person IT department) that is looking for programmers from time to time. The problem is they use Java and Gosu, my experience in Java ended 15-20 years ago, played around with for a bit when it was somewhat new and that's about it. Any professional programming I've done was in Ruby, PHP, Javascript, Python... What's the best way to get started in this case? I'd like to put together a working knowledge of Java before I even start applying, etc.
|
|
#
?
Mar 20, 2017 16:36
|
|
|
n/m
|
|
#
?
Mar 20, 2017 16:41
|
|
|
Bob Morales posted:There's a local insurance company (~400 employees, 60 person IT department) that is looking for programmers from time to time. Learn C# and tell them to switch because Java is trash. They will be impressed by your assertiveness.
|
|
#
?
Mar 20, 2017 16:49
|
|
|
Skandranon posted:Learn C# and tell them to switch because Java is trash. They will be impressed by your assertiveness. Heh. They do some Microsoft stuff too...
|
|
#
?
Mar 20, 2017 19:18
|
|
|
What goes into a good phone screen? I'm starting to screen junior devs, and I don't really know what to look for or how to look for it. There's a separate programming language test, so I don't have to judge that. Right now I let them talk about their programming history, get them to go into details, and ask small questions about whatever tech stack they use (like why are you using Mongo instead of a relational DB). Then I'll ask a couple open ended questions about common situations (like if your website gives you a 404, how do you go about debugging that). And that's my half hour screen. How do other people do this?
|
|
#
?
Mar 20, 2017 21:17
|
|
|
Thermopyle posted:I'm idly considering looking around for a job just to keep my options open (ever since I started making money as a developer I've been a freelancer or transitioned into the position inside a company I already worked at. This means I have never interviewed/job-searched as a dev). It's fine if your GitHub account is littered with trash; I think everyone's is. If you have a GitHub page that links to the selection of projects you'd like them to see, that's nice. If you just provide a couple links in a resume or cover-letter, that's fine, too. I think it would be weird for anyone to spend a lot of time trolling your repos and then form some negative opinion of you. ("This 3-year-old repo with no README has one misspelled commit. Application denied!")
|
|
#
?
Mar 20, 2017 21:29
|
|
|
lifg posted:What goes into a good phone screen? I think it depends on what you want the phone screen to accomplish. In my case, I work for a big company that does all-day onsite interview loops; you have 4-5 devs who each individually interview the candidate for an hour at a time. That's a minimum of ten dev-hours burned per candidate, which can be a huge waste of money if the candidate ends up crashing and burning. In that context, the phone screen is a super coarse filter to make sure we don't waste time on obviously unsuitable candidates. ("Unsuitable" can cover everything from blatant bullshitters, to cute shobon newbies who don't mean harm but are significantly too junior for the job description.) In that context, it's also not the end of the world if a moron gets through now and again, and we should try to avoid annoying good devs with dumb trivia. My phone screens have two parts: * Ask the candidate to write a small amount of code to solve a simple problem in code, using any language they feel comfortable in. (Most of my problems here are one-liners in Python or C#, and 5-10 lines in most other languages.) * Check that the candidate doesn't have any gigantic glaring holes that would nearly guarantee a crash-and-burn when it comes to the onsite interview. What constitutes "a glaring hole" is going to hinge on what your company does and what the job description is; try talking with the people who do your onsite interviews and ask them what they ask candidates, see if they have any memorable interview bombs, etc. Most of my questions here are open-ended things about "tell me, in as much detail as you can, about X," and the only real wrong answer is not having much of an answer. If they have a github, asking them technical details about a project is a good way to segue into these kind of questions without making it sound like it's a test at all. (YMMV, obviously; I don't know anything about how big your company is, or how they interview people. This is just what I do.)
|
|
#
?
Mar 21, 2017 01:08
|
|
|
Hello thread, I'm here to ask for advice about my resume. I have the opportunity to submit it to a big computer graphics company through a former coworker and I want to make sure it's as strong as I can make it. For context, I graduated at the very end of 2015 and have been working in software QA since, and I'm trying to get a job as a software engineer. Even though I've got programming experience in the past and my current job involves some programming (although not enough for me, which is part of why I am trying to switch), I've gotten rejected by a few places very quickly, and there are others that I'm afraid are ignoring me. It feels like opportunities like this are my best (only?) shot at getting a developer job. Here is my anonymized resume, I'd appreciate suggestions or criticism. Thanks! Yaoi Gagarin fucked around with this message at 06:09 on Mar 21, 2017 |
|
#
?
Mar 21, 2017 05:53
|
|
|
VostokProgram posted:e: this was supposed to be a full post i hit the spacebar On Windows at least you can press Ctrl-Z to get it back.
|
|
#
?
Mar 21, 2017 06:01
|
|
|
Thermopyle posted:On Windows at least you can press Ctrl-Z to get it back. It wasn't that I deleted it, I was starting to type it out and accidentally hit something that submitted it. But it's there now!
|
|
#
?
Mar 21, 2017 06:10
|
|
|
lifg posted:What goes into a good phone screen? I determined a list of 5-7 traits I wanted in a new coworker and came up with a few questions which might illuminate each trait. The effectiveness of my questions varied and I was kind of bad at it at first, but having a concrete picture in my mind of what I'm looking for was a big help. I was able to iterate my way to a sensible repertoire of questions over ~6 months of being involved with my company's interview process. My definition of "trait" is quite broad, and could mean anything from "compassionate" to "knows what git is" -- as long as the trait is something concrete and something I could rationally defend if someone asked me why I thought the trait was important. For a phone screen I'd limit it to determining a few traits which would be unacceptable in a coworker and interspersing questions aimed at that in between the generic getting-to-know-you questions. The goal of the phone screen is to filter people who are obviously not suitable, but "obviously not suitable" varies from situation to situation.
|
|
#
?
Mar 21, 2017 06:26
|
|
|
VostokProgram posted:Hello thread, I'm here to ask for advice about my resume. I have the opportunity to submit it to a big computer graphics company through a former coworker and I want to make sure it's as strong as I can make it. Put Skills and Employment above Education. Lose the objective statement. (It's a useless feature of a resume and marks you as fresh out of school, since the only people who tell you to do this are school career centers stuck in the organizational culture of the 1980s.) I don't think there's a need to say "part time" in your title for Company C unless your job title was literally "Software Engineer, Part Time". If you can include hard numbers, do so. Were there any tests in particular you wrote which saved the company a lot of time? Did you improve testing procedures to make them more streamlined? Did you help management understand the value of QA by catching a critical bug which would have cost the company hundreds of thousands of dollars if it was shipped to production? Everyone knows that a QA engineer has probably written test code, what will entice an employer is a story about what kind of impact you've made on the systems you've worked on and companies you've worked for. Also, free advice: don't think of it as places "ignoring you". If they haven't responded to you, it means they're not interested. Companies can be buried in resumes, and it's probably one person who has to filter 100 resumes down to 25 to phone screen on top of all of their other responsibilities. If it took even five minutes per rejection letter to write, address, and send, that's a lot of time for no return. Take silence as a sign to keep applying elsewhere, don't get hung up on waiting to hear back. I think the substance of your resume looks fine, if you polish the presentation of it and apply to a lot of companies, I'm confident you can find a job as a developer.
|
|
#
?
Mar 21, 2017 06:56
|
|
|
VostokProgram posted:Hello thread, I'm here to ask for advice about my resume. I have the opportunity to submit it to a big computer graphics company through a former coworker and I want to make sure it's as strong as I can make it. - objectives are utterly pointless; your objective is to get a job and everyone knows this. remove it and use the cover letter/initial email to give some insight as to why you're interested. - don't include your gpa, a 3.0 isn't worth bragging about (this is not meant as a slight but i wouldn't put it unless you had a 4.0) - put education down at the bottom, people looking at resumes don't really give a poo poo about it if you have actual job history, which should go first / right after skills - what kind of "embedded development platform" in job a, this tells me nothing. maybe elaborate on what sorts of testing code, if only briefly - refactoring is a cute keyword on job c but in reality is pointless fluff, get rid of it - having some links to github or whatever with actual c++ code is gonna be helpful if you actually know c++ because most people who say they do on their resume probably don't - no really, links to actual code is super useful - "experienced with developing software in a linux environment" is an utterly useless statement that equates to "I can install Ubuntu/Fedora/Debian and open a text editor" so either remove it entirely or elaborate on what aspects of being in linux make it any more useful than if you just wrote c++ code in macos or windows. no one gives a poo poo what you develop on in most jobs unless the platform requires something like VS for asp.net or windows apps or whatever. it's 1am but that's just what I notice right now, someone else will probably be able to provide more in terms of substance but this is just lacking a lot of info. if someone technical looks at your resume there's nothing easy for them to go look at like code, so you either have to go heavy and/or very clear on details about what you're actually doing in those bulletpoints, or show them something real that you've worked on edit: as the above person said, and I considered adding this, but nix the part time thing. idiots who initially look at your resume will be confused and a smart person could assume it's because you were in school, but it's easier to avoid any confusion and let them just ask
|
|
#
?
Mar 21, 2017 06:56
|
|
|
fantastic in plastic posted:Put Skills and Employment above Education. Lose the objective statement. (It's a useless feature of a resume and marks you as fresh out of school, since the only people who tell you to do this are school career centers stuck in the organizational culture of the 1980s.) I don't think there's a need to say "part time" in your title for Company C unless your job title was literally "Software Engineer, Part Time". triple sulk posted:- objectives are utterly pointless; your objective is to get a job and everyone knows this. remove it and use the cover letter/initial email to give some insight as to why you're interested. This is exactly the kind of help I was looking for, thank you both. I've made the easy changes and put in a link to my Github, looks like I need to spend a lot of time adding details to my current job. Should I add stuff like Git, SVN, and IDEs to my skills section?
|
|
#
?
Mar 21, 2017 07:39
|
|
|
VostokProgram posted:This is exactly the kind of help I was looking for, thank you both. I've made the easy changes and put in a link to my Github, looks like I need to spend a lot of time adding details to my current job. Should I add stuff like Git, SVN, and IDEs to my skills section? Git and SVN definitely yes, IDEs probably not. I'd be glad to review after you make updates - don't want to repeat what the other two guys said.
|
|
#
?
Mar 21, 2017 13:06
|
|
|
VostokProgram posted:Hello thread, I'm here to ask for advice about my resume. I have the opportunity to submit it to a big computer graphics company through a former coworker and I want to make sure it's as strong as I can make it. Your entire header is taking up waaaay too much space. Also, there's a lot of white space down at the bottom. I think the hierarchy should go something like this Experience > Projects > Skills > Education You should add more information to each job you had. At least one more setence. Lose everything from your education section, except the school, graduation year, and major. And maybe add another project if you have one. And links are really helpful, as others have said already.
|
|
#
?
Mar 21, 2017 15:03
|
|
|
ullerrm posted:My phone screens have two parts: Good point, the real interview is onsite and costly, a phone screen would do well to focus on the screen. Thank you. fantastic in plastic posted:I determined a list of 5-7 traits I wanted in a new coworker and came up with a few questions which might illuminate each trait. The effectiveness of my questions varied and I was kind of bad at it at first, but having a concrete picture in my mind of what I'm looking for was a big help. I was able to iterate my way to a sensible repertoire of questions over ~6 months of being involved with my company's interview process. My definition of "trait" is quite broad, and could mean anything from "compassionate" to "knows what git is" -- as long as the trait is something concrete and something I could rationally defend if someone asked me why I thought the trait was important. This is a method I've never heard of, I'm definitely going to give some thought to "trait based questions". Thanks.
|
|
#
?
Mar 21, 2017 16:58
|
|
|
laxbro posted:While the discussion is on self-taught programming, what do you guys suggest I do after I complete CS50x? I'm leaning towards focusing on web development, specifically something python based like Django. Or would it be better to focus purely on Javascript for interactive frontend stuff, especially since I can use BaaS like firebase app? * I'm doing the in-person CS50x through LaunchCode.org and the tracks offered after the Harvard portion are: Swift Development, Javascript, or C#/.Net. I'm going with C#. On my own/on the side, I'm gonna mess with Python/Django and some front-end skills, I think. Google has a pretty good list of other stuff you should do to round yourself out and continue growing: https://www.google.com/about/careers/students/guide-to-technical-development.html Ruby - http://www.theodinproject.com/ Python - https://www.fullstackpython.com/ * This whole post is the opinion of a fellow programming newbie and should be taken with a grain of salt.
|
|
#
?
Mar 21, 2017 18:27
|
|
|
RUM HAM posted:* I'm doing the in-person CS50x through LaunchCode.org and the tracks offered after the Harvard portion are: Swift Development, Javascript, or C#/.Net. Ruby is trash and on the way out, don't invest time in it if you are new. JavaScript is good, it has a long future. C# is good, and knowing it will make your JavaScript less trash.
|
|
#
?
Mar 21, 2017 20:24
|
|
|
RUM HAM posted:* I'm doing the in-person CS50x through LaunchCode.org and the tracks offered after the Harvard portion are: Swift Development, Javascript, or C#/.Net. I like Free Code Camp: https://www.freecodecamp.com/
|
|
#
?
Mar 21, 2017 20:29
|
|
|
Skandranon posted:Ruby is trash and on the way out, don't invest time in it if you are new. JavaScript is good, it has a long future. C# is good, and knowing it will make your JavaScript less trash. Ruby always did appear kind of niche to me, from my limited perspective.
|
|
#
?
Mar 21, 2017 22:59
|
|
|
When making languages predictions always remember that worse is better, New Jersey beats MIT, yada yada yada.
|
|
#
?
Mar 21, 2017 23:07
|
|
|
Skandranon posted:Ruby is trash and on the way out, don't invest time in it if you are new. JavaScript is good, it has a long future. C# is good, and knowing it will make your JavaScript less trash. Actually JavaScript is also trash, arguably more trash than Ruby, though unfortunately does have a long future.
|
|
#
?
Mar 21, 2017 23:42
|
|
|
Steve French posted:Actually JavaScript is also trash, arguably more trash than Ruby, though unfortunately does have a long future. JavaScript is trash, but there is nothing to take it's place. Learn to love the one you are with.
|
|
#
?
Mar 21, 2017 23:48
|
|
|
Skandranon posted:JavaScript is trash, but there is nothing to take it's place. Learn to love the one you are with. I'm pretty sure that is literally Stockholm syndrome.
|
|
#
?
Mar 21, 2017 23:55
|
|
|
Steve French posted:I'm pretty sure that is literally Stockholm syndrome. It might be a burning trash monster but it's a burning trash monster we know.
|
|
#
?
Mar 22, 2017 00:52
|
|
|
Skandranon posted:JavaScript is trash, but there is nothing to take it's place. Learn to love the one you are with. JavaScript owns, gently caress you.
|
|
#
?
Mar 22, 2017 01:22
|
|
|
Skandranon posted:Ruby is trash and on the way out, don't invest time in it if you are new. JavaScript is good, it has a long future. C# is good, and knowing it will make your JavaScript less trash. I hear from the recruiter I worked with the last time I got a job that he sees much more Ruby stuff but I don't like Ruby at all and wouldn't work in it again I don't think. Also presumably this is all maintaining lovely legacy software which is the worst part of a Ruby project really.
|
|
#
?
Mar 22, 2017 01:29
|
|
|
Just lol if you haven't realized everything you work on and with is garbage that chokes on fantastic processors of the future. Pay is good, though.
|
|
#
?
Mar 22, 2017 01:31
|
|
|
Gildiss posted:Just lol if you haven't realized everything you work on and with is garbage that chokes on fantastic processors of the future. Typing kicks rear end.
|
|
#
?
Mar 22, 2017 01:31
|
|
|
|
| # ? May 17, 2024 22:52 |
|
|
RUM HAM posted:* I'm doing the in-person CS50x through LaunchCode.org and the tracks offered after the Harvard portion are: Swift Development, Javascript, or C#/.Net. Thanks - CS50 ends with flask.py so I'll probably just stick with flask and work my way up to django so I can actually start building some hobby projects I have knocking around. Will probably sign up for one of the algorithms courses on edx or coursera too. I have a (un)stable fed gov't job that I will probably stick with for another year or two (or until I'm 75), but working in tech is the dream. Wouldn't mind taking a pay cut to do something I find more interesting as a junior dev.
|
|
#
?
Mar 22, 2017 01:35
|
|