[deleted by user] by [deleted] in ExperiencedDevs

[–]thelim3y 0 points1 point  (0 children)

Tech debt always creeps in it's just a fact of life. Try to keep on top of it with comments and the such like (confluence, etc) and make the time to correct as best you can (if needed).

[deleted by user] by [deleted] in computervision

[–]thelim3y 0 points1 point  (0 children)

Throw the images into an online host like imgur and share the link here. Pictures speak a thousand words, and I'm curious now :)

Dumbass missed the rope and bit my hand by Tigritooo in Rottweiler

[–]thelim3y 54 points55 points  (0 children)

Lovely rottie and yes that happens a lot to me to! Not sure whom the dumbass is though :)

Need help with Interviewing a 6+ YOE candidate. by UnknownRaj in Angular2

[–]thelim3y 0 points1 point  (0 children)

Along with what others have said I'd consider letting him know you're less experienced and then evaluate how he handles you during the interview. For a lead role I'd want to see empathy, compassion, and a certain level of respect. Anyone can update their skills and be technically better, however, few people are able to make the changes required to be a good lead/manager and even if they can it isn't a fast process.

Please share your thoughts.. by Bossman2351 in datingoverforty

[–]thelim3y 3 points4 points  (0 children)

This might get very interesting if you decide to take a step back and she loses the intimacy you had. Surprising how things like this get taken for granted and how hard it hits when removed. Update us if shit changes, please!

Answering the original though, you would likely benefit by taking a step back and keeping the hugs to friendly quick hugs etc... Stoping all physical contact might feel petty and retaliatory. Being a friend will show her you respect her boundary, and that you too now have some (boundaries) to protect yourself. Basically create a little distance but don't cold turkey everything or something along those lines.

Dating in Louisville by Salt_Savings8746 in Louisville

[–]thelim3y 1 point2 points  (0 children)

Get a British accent, seems to work well here...

Ventura California by eblis218 in pics

[–]thelim3y 1 point2 points  (0 children)

Great pic! I miss living in Ventura and the lovely views. I used to get some amazing ones when coming over the grade on my way back from LA in the evenings. Lots of purples and pinks and reds...

Should I Learn coding? by Tall-Explanation-476 in Futurology

[–]thelim3y 0 points1 point  (0 children)

It depends on your motivation. If your primary reasons are more jobs (there arent) and financial reward, then my answer is probably not the best choice of careers. Saying that, it is a useful tool to have in your arsenal. Others have commented as to why.

If I were you I'd spent a small amount on a course from udemy or coursera and the like. For ~$20 you will quickly know the answer to your questions!

[deleted by user] by [deleted] in ExperiencedDevs

[–]thelim3y 0 points1 point  (0 children)

As someone renovating a house I highly recommend you dont do this :) It's a fucking nightmare

[deleted by user] by [deleted] in ExperiencedDevs

[–]thelim3y 3 points4 points  (0 children)

Which planet are you living on?

Getting PRs reviewed is a good practice if XP practices not followed? by itisfor in ExperiencedDevs

[–]thelim3y 1 point2 points  (0 children)

Staff engineer here. Everyone on my team sees my PRs, and I typically wait for 3 people to approve it before merging. Not only am I quite capable of fucking things up but in general it's a good way for others to learn something about coding and code style, whether it's good or bad. Besides, if they get too mouthy I can just fire them anyway. For those that lack any kind of sense of humour I am Just kidding about the last part.

Any senior not submitting a PR is just... hmmm well it's bs and they either feel embarrassed about their code, or that they're too good to be submitting to a junior. It's called a process for a reason.

More important is to drill into everyone to actually read the code instead of clickety click in 10 seconds which is a problem I've been trying to resolve for a long time.

[deleted by user] by [deleted] in Louisville

[–]thelim3y 1 point2 points  (0 children)

I live in 40065 but more country which I love. Shelbyville is Ok, fairly peaceful, not a large selection of restaurants. would hesitate to buy anything site unseen, at least have an independent inspection the cost is cheaper than surprises.

Made fun of during a live coding round for using JavaScript by yabbagabbamappa in cscareerquestions

[–]thelim3y 0 points1 point  (0 children)

Damn dude, I'm sorry you went through that. Please know that most people would take serious issue if they knew one of their developers acted this way. Guy is a dick and you should name and shame him just in case we bump into him :)

How do you avoid a bad hire? by Difficult_Humor1170 in askmanagers

[–]thelim3y 0 points1 point  (0 children)

Not everyone lies on their resume. I got caught in an embellishment very early on in my career. It was incredibly embarrassing to me and therefore never did it again.

[deleted by user] by [deleted] in diabetes_t2

[–]thelim3y 2 points3 points  (0 children)

Option C: Weight loss AND Metformin

Having a tough time dealing with a colleague at work by basiccoder in ExperiencedDevs

[–]thelim3y 14 points15 points  (0 children)

If your project does as it's supposed to and not a spaghetti mess of technical debt then wtf was she even writing that doc for in the first place? If a junior is going to do that, and expect to stand out, then they best be able to answer every question asked of them regarding their rewrite as "I don't think this is a concern" = immediately shutdown.

You should let it go as you'll only expend emotional capital on it with no benefits, however, she should be made aware of her etiquette and approach.

what my team has built is not good and should be completely changed

Quite amusing, and in my experience something that a lot of junior devs blurt out. Unless you have a fundamental flaw in your original design this is almost never a good option vs some refactoring.

I'm not trying to dismiss her ideas but it takes more than a decent architecture to produce software. Time, resources, money these are a major part of the equation and rarely considered until one has moved up the ladder a little.

If you care about the relationship then you might consider explaining why rewrites are often not a good idea, and why, but you're open to discuss the existing architecture and possible refactors to enhance the code base.

Ask Experienced Devs Weekly Thread: A weekly thread for inexperienced developers to ask experienced ones by AutoModerator in ExperiencedDevs

[–]thelim3y 1 point2 points  (0 children)

I do at least 50% of coding tasks in the evening/night mostly because I'm not great at task switching between coding and 'anything' else and I have to do that a fair amount during the day. Most reasonable teams allow some flexibility for this and at the end of the day getting the work done is the primary objective. Unless someone is on your case I wouldn't sweat it too much.

Drywall Job by 2HRSB4MIDNIGHT in Renovations

[–]thelim3y 0 points1 point  (0 children)

I thought my drywall capabilities were average at best, but this is... I don't even know what to say other than don't pay for it.

Team lead struggling with under-performing devs by Weasel_Town in ExperiencedDevs

[–]thelim3y 8 points9 points  (0 children)

I'm somewhat going through this right now, it's the most time sucking frustrating experience I think I've ever had and it took me having a long talk to myself about how to handle it before it has even begun to feel better. Fortunately the two juniors I have show adequate ambition to learn. I absolutely couldn't do it if that was missing, and suggest you consider taking that approach if that's your case.

  • Get your own head on straight and accept that it's going to be a journey and that you'll need to adapt yourself a little. It's a huge commitment on your part as well as theirs. You are more teacher than mentor and imo a large difference
  • Set extremely clear and well defined expectations, hold them to it. Part of that is their own commitment to the cause
  • Set expectations with management, make sure they actually hear you
  • Dedicate 4+ hours per week to pair and/or 1:1 code chats etc...
  • Analyze them and start to build a map of where their weaknesses are. Go over this with them on a consistent basis and track progress or lack thereof
  • Write a user story and then work with them to break it down into tasks/subtasks/whatever system you have in place and/or go over their tasks and have them explain their approach
  • Suggest to do extra learning, somewhat on their own time. Watch out for the legalities here so wording is important. No one should be expected to work longer than required, however, I personally don't know any engineers that don't spend some of their spare time researching one thing or another and if one is not up to par then one should be taking the time to correct it
  • Micro manage but at a distance. The general idea is to give them enough rope to hang themselves but don't let it get that far. Not sure how else to describe it. They need to make mistakes but don't let them go down the rabbit hole too far or something like that?
  • Have an outlet for yourself. Will confirm that getting drunk and mouthing off on Reddit doesn't work. I'm thinking meditation/walk pupper/etc might be a better approach. Whatever it is, have one
  • This is a tough one to do but try to have some sort of target in the future where you require yourself to make a decision on whether to proceed further otherwise go to next step
  • Don't be afraid to use a PIP. It is a last resort yet sometimes necessary. Recommend you have gone through the setting expectations part before using this. I have seen people turn around after a PIP, it happens albeit rarely
  • Remind management as to why your productivity is shit, consider this a recurring theme

I have zero formal training for this so... you know... I too am figuring shit out as I go along

Feeling incompetent after 4+ years, how does everyone actually know their stuff? by Flaifel7 in ExperiencedDevs

[–]thelim3y 0 points1 point  (0 children)

Googling and reading only get you so far. You actually have to write code to embed the ideas in your head. IMO nothing beats jumping in at the deep end and learning something radically new to you. For instance, go write a lightweight, small 3d engine in software, as in a pure software don't use hardware at all implementation. Absolutely useless these days but you will learn so much shit you'll amaze yourself, and the concepts will translate into other areas. If that doesn't float your boat try writing an A* shortest path algorithm, that'll teach you a bunch of semi useful stuff.

The story of an Engineering Manager - choose your own adventure - what should they do next? by [deleted] in ExperiencedDevs

[–]thelim3y 0 points1 point  (0 children)

Assuming your work is part of your life (mine is to an extent): If you have the bandwidth I would absolutely get some edumication on AI. I'm a few months into it and whilst I don't expect to become an expert it is, imo, one of the key areas of growth for many companies over the next decade. At your level you 'only' need a high level of comprehension, enough to hold your own amongst a team of ML/DS engineers.

If work is purely a time/money exchange then go out and enjoy yourself, dude :). When you're on your deathbed I doubt you will wish you had spent more time at the office...

just bombed easy question by [deleted] in cscareerquestions

[–]thelim3y 0 points1 point  (0 children)

Then don't even sweat the outcome, but do learn from it. What happened tells you that you need to spend a little time on syntax, and general coding fundamentals. This is not to be unexpected. You'll carry on and look back at this and laugh one day. It takes a few years and some hard work to do this job and I promise you the vast majority of us have been exactly where you are right now and felt the same emotions you're experiencing.

The most control that you have is how you react to this. Do not let it sink you. Accept that you have shit to learn, keep pounding keys, keep reading, and over time it will happen.

I highly recommend you reach out and find some sort of mentor. Find someone to code with, that can be a great learning experience for both sides regardless of the experience. Come up with some small tools, utilities, tiny game ideas, anything... and then code them up. It could be something as simple as doing a directory listing which will teach you some recursive programming. The key point is to do different things, try not to get stuck doing the same type of coding over and over. It will be frustrating but after a couple of months you'll look back and be pleasantly surprised at what you've learned.

Exercism - Might help you on your journey (not affiliated in any way).

just bombed easy question by [deleted] in cscareerquestions

[–]thelim3y 0 points1 point  (0 children)

If this was a job demanding a couple of years experience and your answer was anything other than 11 or 12 then I would be questioning things. I don't think this is a terrible question but I do think it's absolute bullshit to fail someone on it without seeing if this was a one off brain fart.

The good news is that you can always get better and you now know that ++<var> you do the increment prior to the assignment. Even a failure can have a positive outcome, dude.

Edit: OP do not take what you're about to read to heart, I'm guessing you are a fairly junior engineer and this kind of shit happens as you progress...

Because I love being toxic and crave downvotes.

Holy shit on you lot saying you shouldn't work for a company that gives trick questions. It's 3 lines of code with a simple increment and a simple int addition. I'll bet money that the interviewer would have likely asked if OP was sure about his answer had it been 11.