|
Pixelboy posted:If you think you're not being evaluated, you're wrong. At least in some places, this is mostly not true. I maintain you cannot "fail" a lunch unless you do something extremely bad, that would likely get you fired or cautioned if you were actually working anyway.
|
#
¿
Jul 18, 2017 22:00
|
|
|
|
| # ¿ May 13, 2024 05:16 |
|
|
Pixelboy posted:You're being evaluated for team fit and personality. Soft skills that don't get surfaced in a tech interview. Making sure that despite (potentially) being technically qualified, you won't be a corrosive drag on the team morale. I understand the notion, just stating that where I work it isn't considered. Our onsite consists of four tech interviews and a lunch. The lunch attendees do not come to the hiring decision meeting, unless the candidate makes such an enormous faux pas it torpedos the standard process.
|
|
#
¿
Jul 19, 2017 21:06
|
|
|
Similar to the other answers, we do a lunch interview to: - be nice to the candidate so they want to work here - let them ask questions and evaluate us - feed the candidate so they perform better in the afternoon sessions - frame the experience positively in their mind, so when they talk about it with their programmer friends they say good things Maybe some other places do it differently but that's the take at my place.
|
|
#
¿
Jul 20, 2017 20:18
|
|
|
mrmcd posted:C/C++ Careful now.
|
|
#
¿
Sep 19, 2017 16:06
|
|
|
This is a load of bullshit, Scala with Spark is cool.
|
|
#
¿
Sep 19, 2017 22:37
|
|
|
Good Will Hrunting posted:did you miss the part where i got shitfaced and hosed a vp level exec at my company's insane drug-filled holiday party literally hours before meeting with the head of HR to discuss how i was't happy with management How big is the company?
|
|
#
¿
Feb 15, 2018 20:26
|
|
|
Good Will Hrunting posted:69 peopple I ask because the bigger the company, the more interesting an event this is. I mean, 69, Nice!
|
|
#
¿
Feb 15, 2018 23:14
|
|
|
Re: UK salarychat, I’m on ~85k in Edinburgh, 11 years experience. Awful compared to USA, but for here it’s okay.
|
|
#
¿
Mar 3, 2018 18:25
|
|
|
ratbert90 posted:I told him for a personal project I wrote almost 100 pages of engineering specification by myself just for my own project, and that if I can do it, there’s no way he could possibly convince me that our company can’t do it either. Whoa, why would you do this?
|
|
#
¿
Mar 4, 2018 16:34
|
|
|
ratbert90 posted:To keep on track and for investors. And was it useful?
|
|
#
¿
Mar 4, 2018 16:47
|
|
|
This is the oldie career advice thread. If you care about advancement in any technical track (as an IC or manger) then it's wise to be mindful of the broader impact of your work on the business, and to learn how to communicate its value in an accessible way.
|
|
#
¿
Mar 6, 2018 20:29
|
|
|
Tell them that Uncle Bob is a garbage dildo.
|
|
#
¿
Jun 12, 2018 23:08
|
|
|
New Yorp New Yorp posted:Yes, I nearly ended up on leave of absence when my mom was dying, but my company is wonderful and said "just take the time off, we'll keep paying you", and I worked on some low-priority, no-deadline projects (mostly internal documentation and other mindless work) intermittently for about 3 months. Then I came back and they gave me a big raise. This is awesome, I worked for a place that did something like this and I appreciated it a lot.
|
|
#
¿
Jul 21, 2018 17:09
|
|
|
CPColin posted:Anybody know of a good course on Project Management, preferably non-video? Lynda is a loving shitheap. I'm desperate to add some PM knowledge to this organization, aside from my boss's alleged PMP certification. https://en.wikipedia.org/wiki/W._Edwards_Deming#Key_principles
|
|
#
¿
Sep 29, 2018 14:40
|
|
|
You should assume it will fall through; luckily you've kept on interviewing (right?).
|
|
#
¿
Oct 3, 2018 21:06
|
|
|
TooMuchAbstraction posted:Alphabet post-mortem template This is similar to the Amazon root cause of error analysis template.
|
|
#
¿
Jan 2, 2019 18:38
|
|
|
JawnV6 posted:Once again, goog and amazon didn't invent the blameless postmortem whole cloth. TooMuchAbstraction posted:Yeah, I certainly didn't mean to imply that this was anything particularly novel; I was just providing a source. I dearly hope that most large tech companies have something similar, wherever they learned it from. Sure, I didn't mean to imply you did; was supplying some more context that this process (not that it was necessarily required) that this is something that technical organizations do on the regular.
|
|
#
¿
Jan 2, 2019 20:29
|
|
|
Uncomfortable with how little controversy there was about code coverage; it is bad!
|
|
#
¿
Jan 17, 2019 00:36
|
|
|
TooMuchAbstraction posted:I'm curious how you get 100% code coverage in cases like this: To attempt to pull the thread up, the way you would cover this is to code against an abstraction for your deserializer (rather than something as concrete as "json.Unmarshal"). Depending on your language and its conventions, this could be an exported 'deserialize' function, or an IDeserializer implementation, etc., and you might import/dependency inject it via some indirection. Then in your test, you mock it with something that succeeds in one test, and fails in another. Doing so is potentially worthwhile to capture behaviour in the failing case in a test, but it's definitely not worthwhile to chase coverage metrics, because as established previously those are bad.
|
|
#
¿
Jan 23, 2019 18:44
|
|
|
prisoner of waffles posted:my few thoughts: This relates to the software design notions of coupling and cohesion.
|
|
#
¿
Apr 24, 2019 22:42
|
|
|
sunaurus posted:
I get about £100k or thereabouts in Scotland. I guess you might say I’d be a senior based on years if experience, although my job title doesn’t say senior.
|
|
#
¿
Jul 18, 2019 23:41
|
|
|
Cancelbot posted:I tried with my AWS interview stuff, god drat I tried. I even started a slight derail from the shite that is continuing to unfold. I've both interviewed there, are am an interviewer there, so I've seen it from both sides. My experience as an interviewee (several years ago) was mostly positive, with only one bad section. In the bad section I didn't gel with the interviewer, and didn't finish answering their question, but did fine in the other sections and ended up with an offer; something to keep in mind if you think a section didn't go well. As an interviewer I do a technical section on the SDE loops, and am a 'bar raiser' on both SDE and other tech job family loops. From what I've seen, most interviewers genuinely make an effort to be accommodating and understanding, and want the candidate to have a positive experience. In terms of preparation, I agree it's worth practicing whiteboarding & writing code in front of others, and remembering to talk the interviewer through your thought process in general. To be honest these things are useful no matter where you interview for a developer role.
|
|
#
¿
Aug 15, 2019 17:26
|
|
|
School of How posted:Code is not something that inherently has to be "maintained". It's not like a sports car that will have parts wear out and need to be replaced. The sense in which a software product rusts is that it no longer meets user expectations. Customers get excited about a new trend, or a successful feature that was once a differentiator is copied by competitors, or the code doesn't run on new hardware, for many other reasons. This is why nobody is buying Super Mario Bros. for the NES in 2019 (outside of novelty retro purchases, which themselves likely don't use the original code). If a product is to evolve with changing customer expectations and demand, it must be amenable to change - likely by a different team of developers. Other than that I agree. If you're writing one off games or apps as a solo developer and you've got no intention or maintaining them, just do whatever works, is fast, and cheap (although, you may find that it's fastest and cheapest to write it well in the first place).
|
|
#
¿
Aug 15, 2019 17:41
|
|
|
|
| # ¿ May 13, 2024 05:16 |
|
|
Pollyanna posted:Well yeah, that’s called a job. While jobs can involve grinding and soldiering, ideally a really good software job should involve solving problems that stretch your creative technical capabilities as a developer, as well as the comms and social issues you’ve described. Good places tend have these opportunities more due to the scale they work at, and it’s pretty good working at a good place with smart and mature people you can learn from and grow with. I’ve had decent success with this at the big companies, but have also lucked out on a small startup before where everything clicked. It’s definitely worth trying the big tech company route next time you change jobs. Amazon, Google, Microsoft, etc., all have teams where it’s better than what you describe, in terms of the opportunity for self development in a high functioning team environment where you don’t only learn effective defensive mechanisms.
|
|
#
¿
Aug 18, 2019 02:15
|
|