|
Thermopyle posted:npm left pad Since this happened, I've created a weekly ritual of node dev shaming in our company slack that revolves around an elaborate set of gifs from this incident. It's one of my favorite things, I really look forward to it every week.
|
#
¿
Oct 1, 2016 17:33
|
|
|
|
| # ¿ Apr 28, 2024 10:34 |
|
|
return0 posted:You sound awful. It's all in good fun, we have slackbots set up for shaming everyone's pet languages / toolsets. Python: stuff about significant whitespace, Objective-C: really just about any method name, Java: all of Java. Not piling on the node hate train here - NPM left-pad was shameful, and also funny. Might as well acknowledge things like that and have some fun with them. speng31b fucked around with this message at 16:22 on Oct 2, 2016 |
|
#
¿
Oct 2, 2016 16:14
|
|
|
qntm posted:Does anybody in your company use Node? It's used extensively. I use it, too - almost daily. left-pad day caused us some trouble. speng31b fucked around with this message at 23:23 on Oct 2, 2016 |
|
#
¿
Oct 2, 2016 23:20
|
|
|
FamDav posted:why arent you versioning all of your dependencies internally? No good reason, other than it's not my decision in all cases. For the products I build and take responsibility for in production, you bet I lock down my dependencies as bytes. Some others are convinced that npm can be trusted, despite outlying incidents. And yet, slackbot never forgets.
|
|
#
¿
Oct 3, 2016 02:17
|
|
|
qntm posted:So you hold a weekly shaming session for developers in your own organisation? It's a joke.
|
|
#
¿
Oct 3, 2016 15:19
|
|
|
Sorry. I am bad at joking and full of regret. I'm generally not a jerk to my coworkers. I work hard to be basically a decent person in the workplace!
|
|
#
¿
Oct 3, 2016 17:30
|
|
|
Pollyanna posted:Really, I care about this so much because I don't wanna piss someone off enough to get fired. I gotta get the rest of my life in order first. Right now, I just wanna write code and do cool stuff. I've read through your posts in this thread, and while I'm not going to type up anything as frankly awesome as Kyth up there, I will say that it seems unlikely your team as a whole hasn't noticed the same frustrations that you're expressing to us. I can't judge your technical competency compared to teammates as expressed here, so I'm not going to try. However - and not to snoop too much - just glancing at the first page of your overall forums posting history it seems like your frustrations with your teammates might be a little bit more specific and serious than some of the posts in this thread alone suggest. You don't seem to have a healthy attitude about your social environment at work right now, and you need to make getting that back into perspective your priority, or your current position might not be salvageable. Remember that you want these people for references even if your current environment isn't the right fit.
|
|
#
¿
Oct 22, 2016 18:37
|
|
|
JawnV6 posted:I had one place that wanted to do a trial 8 hour day as an interview stage. I sent back my contracting rate. 100% correct response.
|
|
#
¿
Oct 25, 2016 04:41
|
|
|
Mniot posted:There's not a lot of overlap. Language-wise Java is about as different from the ones you know as JavaScript to Obj-C. The APIs are quite different. The system quirks are totally different. You might be able to successfully pitch yourself as "mobile developer on all platforms" but I think that if the application you're building is complex or the person interviewing you is an experienced Android dev then you'll get into trouble. Being an iOS developer won't make you an Android developer overnight and vice versa, but there's definitely enough overlap that if you're genuinely interested in learning in either direction and already have solid experience with one, the leap is not difficult. In our team we have iOS and Android specialists, but our goal is to have everyone experienced with both within a year of joining the team (maybe not to the level of writing full apps on their own, but at least maintaining something that exists in a well-defined system). Tldr; Android and iOS have tons of idiosyncrasies that need to be learned and respected, but at the end of the day being a "mobile developer" is definitely a thing that means something other than knowing Swift/Kotlin/Java/Objc. The constraints you work with and the types of user experiences you create are much more important.
|
|
#
¿
Mar 11, 2018 15:13
|
|
|
All this talk about lovely interviews, dang. I've always found that it's easiest just to let the interviewee speak to the products they've worked on recently, problems they've solved, accomplishments they're most proud of. Topics that demonstrate technical chops will come up organically as part of the conversation, and are way more meaningful than quizzing someone on some predefined trivia or spending all your time on a whiteboard.
|
|
#
¿
Mar 20, 2018 03:26
|
|
|
Jaded Burnout posted:I had to learn java recently as a ruby developer and it was fine, except the type system really takes a poo poo when you start doing functional chains with the streams library and nobody on the internet seems to have a solution. What? You can chain typed streams all day. Look at rxjava, it's basically the premise of it. Either way, Kotlin is just Java but better in every way, there's no good reason not to be using it at this point.
|
|
#
¿
Mar 24, 2018 16:27
|
|
|
Plenty of things we can criticize Java for but the use case above isn't one of them. Works fine for that kind of thing, what can I say?
|
|
#
¿
Mar 24, 2018 21:11
|
|
|
There are a lot more opportunities to remain IC out there; it's becoming more and more the path of least resistance nowadays in the opportunities I see popping up. Overall, I think that's a good thing. The trouble comes in figuring out which places embrace IC as a long-term career path and don't look down on folks who choose that. It's also important to be able to ensure that if you take a role that assumes the career path is just IC + $$, and you actually want to transition into management, that's clear early on so you don't settle in somewhere with misaligned expectations. I don't know how founded they are, but my personal fears tend to resemble some variant of this a lot: necrobobsledder posted:... 20 year old me was a faster coder because I actually had the time and mental energy to memorize APIs somewhat, 40 year old me will suck at it probably but be a lot better with people ... I don't particularly think that I'll be worse at the day to day grind of IC at 40, but I'll definitely be less interested in it. I'm already at a point where it's frustrating to see products being developed with management/process mistakes being made that I learned a long time ago how to avoid, and I'd like to be in more of a position to help out with that. My process for the past years has basically been a rinse/repeat cycle of "get hired as senior IC at small to mid-sized company, get promoted to engineering management, company goes under, get hired as...". The first stage of that cycle is like a nightmare where I'm being driven slowly insane by watching teams drive slow-motion into a brick wall, and I want to yell to warn them to avoid it, but nothing but a hoarse squeak comes out. So far I've always ended up back in management within a relatively short period of time of accepting any new job, but the first stage where you're just an IC trying to help people understand the mistakes being made and improve processes is a stressful time. speng31b fucked around with this message at 16:43 on Jun 2, 2018 |
|
#
¿
Jun 2, 2018 16:36
|
|
|
leper khan posted:My problem has generally been my primary employer forbidding moonlighting. Not sure how to work around that. Pretty sure I don’t even own IP I create on my own time and equipment. :/ Don't work for employers who do this, full-stop. Don't make the mistakes that I did where you have to get burned by this sort of policy (also, non-competes) before you realize it's never worth it. Think of it this way - always invest in your future. It's more less expected - or at least not frowned upon - if software developers switch jobs every ~3 years or so. Some of the things that make this possible and profitable are going to be the stuff you do outside of work hours. Never agree to anything that limits your ability to get the gently caress out of a bad situation, or to own what you do on your own time with your own property. speng31b fucked around with this message at 03:41 on Jun 3, 2018 |
|
#
¿
Jun 3, 2018 03:38
|
|
|
I think the industry needs one of those things like "mystery shoppers" but for interviews. People whose full time job is just to interview at places and weed out the absolutely insane poo poo that this thread comes up with.
|
|
#
¿
Jun 9, 2018 23:32
|
|
|
If I find myself in the position of having to interview "for real" and not just getting a job through networking, my usual tactic is just - "that's a cool whiteboard you've got there, but why don't you let me talk about X / show you Y that I've worked on and why it relates your business, why I would add value to your team, why I want to be a part of this place". If I meet a lot of resistance to steering the interview this way - towards just talking like a human and pitching the things I've done or why I'm excited to work there - it's pretty much 100% a sign that I'm on the wrong track. I work reasonably hard to make sure that I have an online presence and portfolio that demonstrates I'm technically capable of doing what I would be asked to do, precisely so that interviews can be shorter and more focused. As both an interviewer and interviewee this approach has always made the most sense and seems to save a lot of time for everyone involved. When people talk about all these nightmarish interview machinations I'm just glad that we somehow have such a different experience with the same industry. Yikes.
|
|
#
¿
Jun 13, 2018 00:54
|
|
|
Hey thread, I'm feeling a bit of burnout right now, mostly just want to vent. About 3 years ago, I transitioned from working at a series of tech agencies and startups to a tech offshoot at a top 10 global fortune 500 company. Long story short, last startup kind of simultaneously collapsed / was acqui-hired by the global company, and most of the team ended up on-board. I now manage an org-wide horizontal engineering discipline that helps out on various projects across the org, and I'm also still able to individually contribute on occasion. I really like working with my team, but for the past year or so all the projects we work on have either been killed or transferred due to churn on C/V suite-level org changes & funding structure. We went from working on a number of projects that were seemingly well-received by execs & customers, to doing very little of value. We've set about working internal tooling and other things of that nature while the org sorts itself out. At a smaller or medium-sized company it would be fairly apparent where we could drop in and add the most value, but at this massive org - and as a horizontal, we don't have much of our own budget - it presents some problems when the verticals that fund us are in a state of disarray. My own duties have shifted towards more or less just sifting through the churn and sitting in meetings with the various vertical team leads to help them sort out the mess as best I can. Our team is well-respected in the org, but I'm finding it hard to make a well-reasoned decision about whether sticking around to see if the org can sort itself out is sunk cost. My own job satisfaction fairly close to an all-time low, but my team is great, and my director-level manager (who I've also worked with at other companies, and I have a good relationship with) is positioned to potentially secure budget and better projects for us to work on in the future. I'm just concerned that the timeline for that happening is on the order of years, and can feel myself becoming burned out and bitter while we wait.
|
|
#
¿
Jan 5, 2020 22:29
|
|
|
|
| # ¿ Apr 28, 2024 10:34 |
|
|
Destroyenator posted:Have you talked to your manager about that? If it’s someone you trust it shouldn’t hurt to make your concerns known and they might be able to give you some indication about what’s coming up politically. Yeah, we have a great relationship and have been working together closely to try to find better projects and secure more reliable budget for the team. Being as involved as I am now in the politics of doing so is messy, though I think we'll sort it out eventually. Not clear how long eventually is, though.
|
|
#
¿
Jan 6, 2020 14:20
|
|