|
Achmed Jones posted:oh! a dynamic fast paced environment where employees must thrive in ambiguity and challenge the status qu- Seriously. Can I get "A stable, deliberate environment where employees can reasonably expect to work on a thing for more than a day before the company's entire strategy changes, and that the things they work on have an outside chance of seeing the light of day?" Anybody? No? Okay then...
|
#
¿
Oct 26, 2021 17:18
|
|
|
|
| # ¿ May 13, 2024 05:31 |
|
|
Good Will Hrunting posted:No idea how people are productive on code problems after work. I'd have to quit again or get fired, or accept a big pay cut, to get this level of TC again. As a senior dev I currently spend more time discussing requirements and technical feasibility with Product/other management, and higher-level design, than I do writing code. At this point I code problems for interview prep would probably be rather stimulating, especially without the added pressure of being unemployed and NEEDING to do well on this or that interview exercise.
|
|
#
¿
Oct 28, 2021 23:01
|
|
|
AgentCow007 posted:I've been at my 'junior software developer' job for a year now and still haven't touched a line of production code. Yeah honestly you should be able to land another job as a junior/associate without a lot of trouble after a year working. There's a world of difference in an interviewer's eyes between "junior candidate with 1 year experience" and "fresh grad, same as all the other fresh grads, just throw a dart." I would definitely start looking though, you should be spending the majority of your time coding at your level. They're wasting your time and staying there is going to hurt your career long term.
|
|
#
¿
Dec 22, 2021 10:49
|
|
|
asur posted:Is this really a concern in software? Short term and long term disability along with FMLA and a good healthcare plan should alleviate most concerns and it's not uncommon for a company to give more than that if you need it. Sure, if your company happens to act in good faith, play by the rules, and recognize the value of retaining senior employees.
|
|
#
¿
Mar 6, 2022 21:18
|
|
|
When we switched to fully remote, I tried to keep things moving and under 15 minutes in the morning. Pretty quickly, I got a lot of feedback that the vast majority of my team prefers to not be rushed in the morning, which usually results in 30-45 minutes. Requirements clarification happens there, design discussion happens there, as well as personal chit-chat and making fun of the executives after their latest all-hands announcements. Everyone seems to want the interaction that we don't get as much of during the work day since we're all remote. At my last job, when we were in the office and all standing around a projector while the manager went down the extremely long list of in-progress tickets one at a time, it was 45 minutes of hell. But oddly enough, in this situation, it doesn't feel bad. I think I'd personally prefer to keep things short and deal with the other questions in other, smaller meetings, but ultimately it works for us. We're one of the more successful teams in the company in terms of meeting goals, building products that function in time for the people that need them (usually the larger project is months behind and we get to say "yeah we've been ready for the last 3 weeks" when someone asks why thing isn't done).
|
|
#
¿
Apr 16, 2022 19:05
|
|
|
TooMuchAbstraction posted:Look at the camera, try to project a sense that I am paying attention to the person that is currently speaking. I mean, it's not like I'm not paying attention when I look away, but people tend to get the wrong impression. I stand while working and I pace back and forth on camera all the time, whether I'm talking or not, which means not only am I not looking at the camera, I'm going in and out of frame. I've never received any negative feedback about it. Granted, I spend most of my meeting time with team members; we all know each other well at this point. The one situation that occurs regularly where I modify my behavior a bit is a 1:1 with my direct manager, because it's a bit more of a personal conversation. I think that people like us (technical problem solvers) tend to worry a lot about things that we might think could be problems, but aren't actually problems most of the time.
|
|
#
¿
May 2, 2022 03:53
|
|
|
TooMuchAbstraction posted:I've received direct feedback that just closing my eyes (which I do to help concentrate on what someone is saying) is being read as being dismissive of what [person providing feedback] was saying. Now, I was able to tell that person "I'm just doing that so I can listen to you better", and I do think that in a work context it'd be at least a little different, but it's still very easy to misinterpret body language over video chat. Ah, that sucks. At least it sounds like you are able to correct misunderstandings, and if you're working with otherwise reasonable people you should be able to set expectations over time.
|
|
#
¿
May 2, 2022 15:09
|
|
|
Good Will Hrunting posted:We have now opened 2 more roles at the level I should have been promoted to, in addition to the role we just filled there, with someone that has a PhD and only 3.5 years of experience at a real company. I asked my manager why not promote internally and his answers were the most non-answers imaginable and they 100% just want to milk my contributions at my current level instead of recognize me. Complete joke. So excited to leave. I like to play the competing game, "How little can I contribute and for how long?" It's the phase in the employment cycle where you can learn new tech instead of just gain a deeper understanding of the arcane rules of the specific industry niche your company du jour happens to be in.
|
|
#
¿
Nov 1, 2022 10:51
|
|
|
I will point out that while all of this advice is good and correct when it comes to calculating taxes, budgeting, and comparing your current gig to potential future ones, the equation changes when you're actually negotiating switching jobs. "Well, I have RSUs and options worth [almost naively optimistic value] with my current company, can you match that in a signing bonus?"
|
|
#
¿
Nov 14, 2022 18:38
|
|
|
downout posted:I have no idea if elon has a software background or even claimed to, but that request should make any engineer that has experience and isn't tied by a visa to gtfo. Caring about the number of lines of code committed is a loud declaration that one does not have a software background.
|
|
#
¿
Nov 19, 2022 19:15
|
|
|
Erg posted:I think people are talking about earlier when he was telling people to print out their last 50 pages of code That's what I was talking about, yes. I hadn't realized we were dealing with two separate events.
|
|
#
¿
Nov 19, 2022 22:05
|
|
|
The more theories I see from confident people about this, the less I worry about my job prospects.
|
|
#
¿
Dec 7, 2022 18:41
|
|
|
Rocko Bonaparte posted:I don't know what to think about this switch to senior positions or whatever because they all demand lots of very specific skills and experience that nobody has. Most senior jobs don't actually demand anywhere close to what they list on the posting. Yeah sometimes algorithms will gently caress you over; I recommend putting a bunch of keywords on an "other skills" kind of section at the end of the resume for the robots to read, just tell something approaching the truth if a human asks you about a specific one. But I can also tell you that I've had better experiences with recruiters as a senior candidate than I did as a junior.
|
|
#
¿
Dec 17, 2022 20:25
|
|
|
Yeah each gig has its own host of problems. For me it really just comes down to how many meetings I need to have and how much engineering I actually get to do.
|
|
#
¿
Feb 9, 2023 20:41
|
|
|
raminasi posted:I wonder if I’ll ever get to a point in my career where I stop thinking of this kind of thing as depressing and grim. This isn’t a dig at you, props for playing the game, but “The celebrated centerpiece of my promotion narrative was me doing something that had absolutely no material impact on anyone at my company” just reads so bleak. As Artemis spoke to, it helps when you change your perspective. At any given job, I get fulfillment on a micro scale: I fix a nasty or tenacious bug, I come up with an elegant implementation for a specific feature, I teach something to one of my peers. If I'm thinking about career progression, I'm thinking about either broadening or deepening my own knowledge of a language or technology. I'm teaching what I know to the young'uns (the act of which, again, deepens my own knowledge). Sometimes you can get promotions and raises from within, by actually doing good work that gets shipped and used. But I've seen a lot of bad, uncoordinated, uncommunicative leadership over my career that prevents that kind of thing from happening a lot of the time. I choose to care about my own personal growth, rather than the growth of a company - what is ultimately a faceless, lifeless machine. Maybe one day I'll be part of a tiny company where everyone is equally invested (literally), and my perspective will shift accordingly. But zero-point-zero-three percent equity that vests over 5 years is not "We're all in this together!" Meanwhile I'll get my fulfillment, as I said, on a micro scale at work, and otherwise via non-work activities.
|
|
#
¿
Feb 20, 2023 11:15
|
|
|
CPColin posted:Dear CEO, On the other hand, sometimes CEOs read huge tech news, and I would much, MUCH rather them come to me, taking what in a case like this would amount to a few minutes of my time, instead of sounding an alarm among the other executives and causing a big stink that will linger for weeks. Hell, executives routinely discount the experience they're paying me for, so having them actually seek it out is a notable event.
|
|
#
¿
May 26, 2023 20:38
|
|
|
Hadlock posted:Agree $105k/year, no 401k match yet while we run lean but maybe soon!
|
|
#
¿
Jun 13, 2023 01:14
|
|
|
Ensign Expendable posted:Re: interviewing in Python Hell of a leap from "this is one language the candidate felt comfortable with" to "doesn't know any modern language." That's without addressing their definition of "modern" if they aren't applying it to Java.
|
|
#
¿
Aug 10, 2023 01:52
|
|
|
Guinness posted:Yeah this exactly. n = 2 use cases is often not enough to generalize and then when the third or fourth use case eventually come along it gets shoehorned in to a bad abstraction I call it "dying on the hill of DRY." I've also continuously run into generalizations that were solely there for future proofing. You know, "we might need to account for this case in the future." My most successful (by my standards) team to date became really disciplined about only solving the problem in front of us, and it led to better code, deployed faster. The vast majority of the time the future case never happened. When it did, and we decided that it justified a refactor towards a generic implementation, we had those specific cases already deployed and debugged and surrounded with unit tests. Made it safer in my opinion.
|
|
#
¿
Nov 22, 2023 19:35
|
|
|
Vulture Culture posted:What's really neat about this is that the tests on your first pass almost certainly documented the most specific cases that were necessary in production. The generic implementation probably didn't do this half as well or as obviously Exactly. You get your first and arguably most important behaviors, blueprint them with tests, and later you can refactor with confidence.
|
|
#
¿
Nov 22, 2023 23:08
|
|
|
|
| # ¿ May 13, 2024 05:31 |
|
|
leper khan posted:take the example in your edit. you could use that to sell yourself as being comfortable in uncomfortable situations. you didnt in your text, but you could. start by cutting the self-deprecation and focusing on the value you delivered and what you did to achieve that. your story plays better in the reverse of how you said it [hired for 3 summers, started not knowing anything, tenaciously looked for info on how to succeed, worked alone without significant help, they probably didnt want to hire me but it worked out for both of us] Exactly this. Rewrite that paragraph so that it transmits, "it was a challenge, and I overcame it" rather than "the company only had bad options, but at least I didn't gently caress it up too badly." You can be honest about your experience without being down on yourself, and the fact is that you have succeeded without your hand being held already. Talk that up. The ability to research is a huge part of this career, whether you're on your first gig or your tenth.
|
|
#
¿
Apr 10, 2024 20:41
|
|
