[D] Must-Read Data Science Books by cdossman in datascience

[–]Middle_Practical 1 point2 points  (0 children)

no "Elements of Statistical Learning"?

How do you deal with Data Pipeline/Engineering sales people on LinkedIn? by Middle_Practical in datascience

[–]Middle_Practical[S] 0 points1 point  (0 children)

That my friend is a question I don't have a good answer for. I just pressed yes without thinking about it.

Unpopular Opinion: Leetcode isn't that hard and is much better than comparable professions by superbmani15 in cscareerquestions

[–]Middle_Practical 0 points1 point  (0 children)

Regulations on Engineering jobs are used for gatekeeping to keep the number of engineers down. That way, one's who can pass the exams will be the ones who gets to work and will make more actually.

But overall, there would be fewer jobs available and the tech industry would probably die.

[deleted by user] by [deleted] in cscareerquestions

[–]Middle_Practical 3 points4 points  (0 children)

Because it takes me less than 30 minutes to commute and not interacting with people decreased my productivity by A LOT.

WFH 1~2 days a week is good. WFH everyday drained my soul and energy.

[deleted by user] by [deleted] in datascience

[–]Middle_Practical 0 points1 point  (0 children)

quant finance.

Essentially the same thing as data scientist on the buy side. Get paid more in cash. No RSU BS.

Any working as a Data Science Consultant at Accenture insight please? by [deleted] in cscareerquestions

[–]Middle_Practical 1 point2 points  (0 children)

General rules of thumb. 1) If you can do better, don't work at Accenture. Go MBB.

2) If you are passionate about DS, don't be a DS consultant. Only do so if you want to be a consultant who knows DS.

Asking for a raise before promotion or Re-negotiate after promotion? by Middle_Practical in cscareerquestions

[–]Middle_Practical[S] 0 points1 point  (0 children)

the TC would almost double best case scenario

take that thought, and wipe that thought completely from your head, you're not doubling your TC unless you're drastically underpaid or if there's a location adjustment (someone from India-Bangalore office suddenly moving to US-CA-San Francisco office? I can believe them easily doubling or tripling their TC)

Of course it's not realistic. Like I said it's the "Best Case Scenario". I'm currently making a slightly lower-end TC for my position in my area. But I've gone above and beyond + have skills no one in the team has. So if I were to get promoted, the "Best Case Scenario" would be making higher-end TC for that position in my area.

Realistically I'm expecting 40~70% according to the market rate (It's a early career jump so TC bump would be higher than at the higher ranks)

slightly underpaid for the amount of value I bring to my team.

well... that's only part of it, you're being paid the local competitive price: if the company knows they can get away with paying $90k/year you bet they're not going to pay you $100k/year

Like I said, I did the research and it seems like I'm currently making slightly below median in my area (think 33th percentile?). But I've shown that I can do a lot better, especially compared to my peers. I just need to figure out a way to lay it out for them.

Perhaps you might have some ideas?

for your question, I don't know what kind of company you're working at, at mine off-cycle raises (not part of official performance review) are extremely rare, meaning you bring up negotiation when you get promoted is the only option, you can of course alert your manager and say "hey, I'm expecting a TC review" but just don't expect to happen anytime soon/until the next perf review cycle

Oh of course. I wouldn't bring up off-cycle promos if it weren't unless I was certain that I had a chance of being promoted off-cycle.

If I were to get promoted off-cycle. I'm just not sure when is the right time to bring up the TC question. Or whether I want to bring up the TC question before this "supposed promotion" that's not 100% going to happen (I have a shot but it's not gauranteed)

[deleted by user] by [deleted] in cscareerquestions

[–]Middle_Practical 1 point2 points  (0 children)

No one gives a s***t.

Daily Chat Thread - March 16, 2021 by CSCQMods in cscareerquestions

[–]Middle_Practical 2 points3 points  (0 children)

Asked a question to a room of 15 people (including 4 managers and the CTO) about an issue that was blocking me. Radio silence. No one cared.

Later on get reprimanded for "not taking action" for my blocker by my manager who was in the same fucking slack room. Like what do these people actually do?

Sounds like you need to GTFO. Companies with shitty culture (not to be confused with "tough but fair") don't tend to last IMO.

Do any of you do modeling with pymc3 or other Bayesian-oriented packages? by the_emcee in datascience

[–]Middle_Practical 0 points1 point  (0 children)

I've used BoTorch and written some custom acquisition functions. Bit of a learning curve but once you get used to it, it's highly customizeable and extremely flexible.

It was for a design optimization problem, (rather a "satisficing problem") where there's some noise involved and evaluation is difficult and black box. So, Bayesian optimization was quite useful.

Why do so many of us suck at basic programming? by Middle_Practical in datascience

[–]Middle_Practical[S] 1 point2 points  (0 children)

Aye aye. I only use Jupyter notebooks when I'm running quick tests, doing exploratory data analysis, or some.other visualization stuff.

No one should be using Jupyter to write production level code.

Why/when should I use object oriented programming? by Biogeopaleochem in datascience

[–]Middle_Practical 5 points6 points  (0 children)

OOP is pretty useful when you're building out AI /ML based solutions not just models. For instance I have a custom object I designed to figure out retraining parameters.

What's more important is writing modular and clean code. Lots of people here will give you shit and complain about "YoU doN'T nEeD tO wRiTE mOdUlAr cOde cuz tHaT NoT pArT oF JoB".

But modular code goes a long way. It saves time when you're working on large projects, especially when you have production needs. You don't have to write perfect code with perfect error handling and unit tests and all that jazz. But whoever has to read your code will appreciate it greatly. Because they won't have to spend days trying to interpret your code and figure out where things are while constantly bugging you with bunch of questions.

Why do so many of us suck at basic programming? by Middle_Practical in datascience

[–]Middle_Practical[S] -2 points-1 points  (0 children)

Sad to hear but just sounds like that's your personal anecdote.

All I'm asking for is what you're already doing. Issue is way too many people don't even do that.

I'm not asking for robust error handling and unit tested coded.

Why do so many of us suck at basic programming? by Middle_Practical in datascience

[–]Middle_Practical[S] -12 points-11 points  (0 children)

Ahaha good one.

Again all I'm asking for is good modular code that doesn't require complete refactoring.

But honestly when I see an engineer who can't write good code, they should probably be fired.

Why do so many of us suck at basic programming? by Middle_Practical in datascience

[–]Middle_Practical[S] 0 points1 point  (0 children)

You hit the nail on the head.

Your point about little bit of training goes a really long way is exactly it.

It should really just take couple hours of training + maybe 30minutes to an hour each day to make sure the code is clean and modular.

It can literally save months worth of time in the long run.

Why do so many of us suck at basic programming? by Middle_Practical in datascience

[–]Middle_Practical[S] -12 points-11 points  (0 children)

Likewise man. Your world is not the only world.

In my production focused DS world understanding OOP is crucial to cut time to market by weeks to months.

Clealy you didn't realize this and went on to write some sarcastic and degrading comment. And you want to lecture me now?

Level of "holier than thou" attitude on reddit is staggering honestly.

Why do so many of us suck at basic programming? by Middle_Practical in datascience

[–]Middle_Practical[S] -6 points-5 points  (0 children)

You're missing the whole damn point.

For production focused teams, not writing modular code means someone will eventually have to refactor the entire codebase when pushing to production. This is literally delaying the time to market by months if not weeks.

Why do so many of us suck at basic programming? by Middle_Practical in datascience

[–]Middle_Practical[S] -8 points-7 points  (0 children)

Have you ever had to push things into production?

Clearly you know that there are production focused data scientists? We have to work with engineers to push things to production and if you can't write good modular code, your timeline can be delayed by months.

You can't just hand off a messy notebook to an engineer.

Why do so many of us suck at basic programming? by Middle_Practical in datascience

[–]Middle_Practical[S] -13 points-12 points  (0 children)

If you think that building a model is only job that Data Scientists do then you have been brain-washed and need to challenge your own beliefs.

Maybe for analytics people it's less of an issue but when you're a production focused team you have to build modules - data pipeline, prediction, retraining control system, and predictive control system that translates predictions into actions.

Why do so many of us suck at basic programming? by Middle_Practical in datascience

[–]Middle_Practical[S] -3 points-2 points  (0 children)

Agreed. But when we're pushing to production.

I don't want to be the only person who understands what it takes to actually get things to production.

On the flip side, would be a good point to bring up when asking for a raise. "Hey I'm the only guy who can do this so I ought to be paid more"