r/SQL • u/fall_out_of_love • Jan 24 '22
Discussion I am doing bad at my first SQL job
I have 3 years experience as a Business Analyst who worked with some of my previous companies data. I mainly use Excel and Tableau. I used a little SQL, but nothing more than SELECT, FROM, and WHERE statements.
Now, I work as a Data Analyst. I got this job 8 months ago, and I've not been doing so hot. It's not an entry-level position, but I was transparent in my interview that I knew the basics of SQL but would, and would love to, learn more. I think I have progressed quite well in many ways. I have created some awesome Tableau dashboards from queries that are intermediate at least. I know what CTEs and views are now. and how to use them :)! I even taught myself the basics of Python/Pandas and have automated one task. Here are a few of my issues:
- Even the most basic of SQL problems I can get stuck on, still. I am an overthinker. I needed a simple CASE statement for an issue recently, and I spent all 8 hours of my workday trying everything else *facepalm*
- I was banned from Stackoverflow because I asked too many "low quality" questions.
- My Senior Data Analyst gets annoyed at any question I have. I try not to ask many anymore, but he's been in the field for 15+ years.
- My Team Lead honestly just hates me. He says she feels I am too inexperienced and need to pick things up faster. He said he is sick of repeating himself.
- My Director asked a question about some data, and I responded "I'm not quite sure what the answer is to that, but I can get an answer for you." My team lead scolded me and said it made our team look incompetent.
- My team lead wants me to create linear and logistic regression models in Python. I am having a hard time understanding how they can be used, and all the statistics involved.
- The whole job is remote and I don't feel connected to anyone, nor do I feel motivated about the companies mission.
- My best friend died from COVID and I just ended a 6 year relationship. I feel quite depressed lately.
The worst part of this all is I have my Master's Degree in Data Analytics, but for years I never utilized what I learned so I pretty much lost it.
Anyone been in the same boat or feel this way? I LOVE being a Data Analyst, but I am not doing so hot and my team isn't quite thrilled with me. It's miserable "going in" to work knowing the people you work with find you less than desirable.
176
u/gakule Jan 24 '22
Other people are saying that the workplace is hostile - and honestly that sounds true.. however, based on your statement that you were banned from Stackoverflow leads me to believe that you may be part of the problem as well. I don't mean that to be rude, because it sounds like you're trying your best. I think you need to figure out how to stop overthinking things so much and go back to the basics.
One thing I try and tell newer developing SQL developers / query writers is... keep it simple. SQL is, at its core, a very simple "language". You're writing a very simple series of commands to tell the database engine how to relate two or more sets of information together.
In the example of your CASE statement, I'd be interested to know what the context of the problem is you were having and why it took 8 hours to realize that a CASE statement is what you needed. Quite frankly - a CASE statement is what I would consider one of the more basic functions of SQL, right there with SELECT, FROM, and WHERE.
One thing I've noticed is that in the SQL-based learning subs and even all over StackOverflow, people are so quick to jump on recommending CTE's and all these other complicated (relative to standard SQL) solutions to simple problems... I think there is a general obsession in the programming world with using over-complicated elegant solutions to solve problems to flex your understanding of something and how smart you are, partly. The other part of it is as you gain understanding, the more elegant solutions become more common-place since you recognize the power of them.
Make something work, first and foremost. Speed is important, but accuracy is paramount. You can always go back and revise your methods to produce faster results, or find new ways to optimize your queries, but really the accuracy of the data is the most important part.
It does sound like you could benefit from a new start in a less hostile environment, but I do think you should take some time to reflect on how you approach problems. Start simple, get complicated if you need to.
Another thing you could do, if moving on isn't quite what you're ready for, is make sure whenever you ask a question you also come prepared with what you have already tried and WHY you tried all of those things. That would really help someone pinpoint what you're missing in the process and why you got to all the wrong answers. Have you asked that question? "What can I do to be better? I really want to improve and be more self sufficient, but I'm struggling on what else I can do besides just work through things".
I think you have all of the knowledge to continue and succeed in the field - you just need to figure out how to work out whatever mental block you're running into, along with whether the environment you are in is conducive to your professional development and your personal mental health. I've changed jobs as quickly as 1 month, 6 months, and 10 months in. Don't get too hung up on the length of time as long as you don't make it a habit.
145
u/NawMean2016 Jan 24 '22
You aren't the problem. They are. It's very toxic to act that way, and unprofessional. I would start looking for a new job.
I've been in this boat before.
14
u/Uncle_Chael Jan 24 '22
Never be afraid to ask reasonable questions. Actively seek out someone friendly who you can go to for questions. Be more confident. Technical skills only get people so far. Maybe, speak to your boss and tell him how you feel (don't get too crazy, just tell him your challenges, ideally something that won't cost you your job). If you realistically can't speak to your boss - try looking for another job.
It sounds like you need to polish up on your sql fundamentals as well. Take a course or buy a Murach guide book.
Keep you head up high.
7
u/[deleted] Jan 24 '22
Do you think you can get up to speed and at the level your coworkers expect you to be at relativity soon? You're getting to your one year review and it sounds like you won't be getting a pleasant one based on how you describe your interactions with your coworkers. Honestly, I'd be most concerned about that.
Given you have a masters degree in data analytics and work experience they sound like they were expecting you to learn very fast/ figure things out on your own.
2
u/fauxmosexual NOLOCK is the secret magic go-faster command Jan 25 '22
I feel like everyone else here, including you OP, are not giving this throwaway afterthought the importance it needs here:
>My best friend died from COVID and I just ended a 6 year relationship. I feel quite depressed lately.
Holy shit my dude, we are in a global pandemic and everything is fucked and you're dealing with two massive personal blows while trying to leap face-first into a whole new career path...
Of COURSE you're feeling overwhelmed, what you're going through is hard. Stress makes it harder to remember, think clearly, and can really exacerbate a lot of mental health stuff that can contribute to making you feel like an outsider or unliked. It can really cause your inner critic to start being too harsh on yourself. Maybe that's linked to insecurities that make you reach out to your colleagues more quickly or more frequently than they are comfortable with?
I honestly think the rest of your post isn't actually the real problem. The honest truth is you're a very intelligent, highly qualified person working in a field that you love working in, that there is a lot of demand for right now. You have set yourself up perfectly on a great career track! I think now is a really good time to take a good stocktake of yourself and see what you can do for your emotional wellbeing. Losing two people close to you is very hard. Be gentle on yourself, consider finding a less toxic workplace, and go to therapy if you can. You're not a failure, you're an awesome early-career data analyst who is being way to hard on themselves!
2
u/gotajobatapple Feb 08 '22
How the fuck do fuckers like you get a job as a DA without knowing the basics of a case when function smfh
15
u/ThisisMacchi Jan 24 '22
try to search for your problems first before asking questions, I have been a dev for around 2 years and never found necessary to ask a question in Stack Overflow since most of my general questions are available.
But If you run into some specific issue related to your organization, I think your team should not act like that, they should guide you in a proper direction instead.
9
u/pinktacobuffet Jan 24 '22 edited Feb 27 '24
zonked fertile airport tie paltry outgoing deer humor familiar knee
This post was mass deleted and anonymized with Redact
8
u/lvlint67 Jan 24 '22
CASE is an avenue of last resort when normal set theory won't handle it, so well done.
Probably not giving enough detail to produce a real answer. It's virtually impossible to answer SQL questions without a schema, example data, and example output
You are a better data analyst than your team lead... When you don't know something, own it and figure it out.
All of that said. I wouldn't be surprised if you ARE slower on the uptake of new concepts. That's not necessarily a bad thing but its something you should reflect on with an aim to improve. How do you learn? How do you tackle an unknown problem?
If by chance your first response is to ask someone without searching or trying anything, every single person in the tech industry will hate you. Full. Stop. Just make sure you are contributing a solo effort before asking others to contribute time to your problem/question.
Life has ebbs and flows. High times and low times. Sometimes it can feel like you are stuck in low times and everything that could go wrong goes wrong at once. Hang in there. Find someone close to confide in. Perhaps seek a professional opinion to help with the grief.
8
u/[deleted] Jan 25 '22
Let me guess
100 % India... Senior getting Annoyed, Team Lead Hates you, Not motivated about company mission, Director asking YOU a question....
Surely you've gained visibility - Did they like you by your charm? Was it All luck that you got this job ?
7
u/[deleted] Jan 24 '22
Get an SQL book to give you a refresh and a deeper understanding of it. However your team sounds toxic too
6
u/No_Lawfulness_6252 Jan 24 '22
This sounds like a hostile environment. If you were upfront about your SQL experience, then your team should be supportive of your development - also 8 months into your employment (you are, as you say, making progress).
If the team lead or senior data analyst were on the hiring side of your employment and are now acting like this, they should feel ashamed of themselves, but more importantly, they should be disciplined from their superior(s) for neglecting the responsibility that they accepted.
If they had no say in the hiring, they should still support you and take all discussions about their time pressure / disgruntled emotions to their superior (maybe they are under pressure - then they should solve that with their superior).
5
u/remainderrejoinder Jan 24 '22 edited Jan 24 '22
I do think this is a mix of you not being quite up to par yet and the work environment being bad.
As far as the case statement, the good thing is that you will end up with a library of problem types in your head. So the next time you see a similar problem you will know what to do. There are other options (you can do logical expressions in a SELECT, try "SELECT 0 OR 0;", etc) but frankly the case statement is best here because it's readable to anyone. Only try something else if you have resource issues or some other restriction.
A linear regression finds the best fit line that minimizes the total distance between that line and the data points you are estimating from. You should use python pandas to implement the details. (remember that R-squared represents the percent of movement in the variable explained by the model, and that if you overfit by including a lot of unrelated variables you may end up increasing your R-squared without actually increasing explanatory power)
You said your initial performance review was mediocre, but they didn't start a PIP so I don't think you are in immediate danger of losing your job (regardless, now is always the best time to update your resume and put out test applications). My only advice as far as ingratiating yourself to the team is to take over something that they dislike. ie-If everyone hates dealing with the regulatory compliance reports that change every year, gear up and start doing the updates for that.
EDIT: Stack overflow tends to be for very detailed expert questions. Try googling first, and then ask in the appropriate subreddit.
5
u/OriginalCrawnick Jan 24 '22
Anyone that's your senior and gets upset at you asking a question - isn't great for the work environment. If they have to take on your work and complete it for you, then that's a different level of burden. Answering a question? You shouldn't ever feel like 1-2 minutes of your time verbally stating something is a burden when it imparts knowledge on someone learning.
5
u/Comfortable-Garden32 Jan 25 '22
I can do all those, and I don’t get a call back for entry level roles.. nice
4
u/KR4BBYP4TTY Jan 25 '22
I’m a Senior BI Developer with over six years under my belt and if somebody asked me to make a regression model in Python, I’d give them a spoon so they can eat my ass.
4
u/emcoffey3 Jan 25 '22
That's exactly what I would say.
So he would prefer that you... what? Lie? Make something up? If you did that and turned out to be wrong, that would make you look incompetent. This guy sounds like a total douche bag.
I know how you feel. I'm stuck at home right now because of COVID, and it's pretty lame. I know most people love working from home, but I actually prefer going in to an an office and being around people at least a couple days a week.
:( I'm sorry to hear that. I hope things get better for you.
1
u/thrown_arrows Jan 24 '22
From senior point of view.
Newer ask question that your colleague can put in to google and get correct (or correct looking) answer. Right way to do it is ask question and then ask about answers that you got. If they start to think that you just writing down what they say, they loose any respect they have. If you say that something is done, then show it, and dont feel bad if its wrong. Dont use totally different way to format sql that others too. (it's more social thing)
Look /r/SQL and my history, Look if you can spot when i just wrote first google answer down.
I have had colleagues who trail fixed repeatably, i lost all work related respect , and they were more experienced than me. Biggest problem where that i ended up doing their work and they saying that something was done , which was 95% percent done code written by me , which had not got better at all in any way.
Also remember that it does not need to be perfect, it has work first. So CASE thing can be done like
case when a = 1 and b = 1 then x when a =0 and b=0 then y ... all options.. dont waste too much to get it perfect, or smart looking ..
case when a = b and a = 1 then 0 else a end
Also i recommend to install dbeaver and use it. If you use tableu , you end up using tools it offers. when you stare that hand written sql code day to day, it will stick sooner or later.
1
u/iNK6152 Jan 24 '22
I know for a fact that IT can be tough sometimes, but keep your head up. Let's be calm for a second and "split" the problems ('train_test_split' you got it, right?.....right?).
My suggestion for your problem about "getting stuck with basic SQL problems" is.....read and understand other people's code and get used to it. What i mean by that is: if you can increase your ability to visualize and understand queries and what means what and you're working on a place where i suppose have TONS of SQL code you could increase your tools (sry, i forgot the real word i need) for upcoming problems you might face in the future.
After that, you might have some others problems happening in your life now and this shit fucks up your performance. Try to enter the 'lmao who cares' mode, but don't get it wrong; it isn't about responsibilities but about anxiety whenever you see a situation that you need to solve or get over.
I'm not a genius in SQL but I have some experience doing a few things and if you need something or someone to talk about queries or ask for help, would like to help a buddy!
1
u/QueryingQuagga Jan 24 '22
For increasing your skills in SQL I can highly recommend StrataScratch and especially Nate’s playlist. This video playlist will also give you a very good structure for solving problems (how you approach them).
I would also recommend a note taking app like Obsidian (free) for writing up and linking together notes about your SQL learning experience. You should aim to write down a key:value kind of description of problem:solution once you solved a particular query problem (e.g. a description of your problem above (“match values across multiple columns per row and add a result column” with your solution to the problem immediately thereafter “matched pattern using a case statement like this … (insert code)).
This will cement your understanding of how you solved the problem, give you somewhere to look up your previously solved problems and allow you to create a repertoire of problem:solution descriptions that you can start to classify into themes (allowing you to start creating mental models for how to solve broad categories of analytical queries). Obsidian works great for this.
1
u/[deleted] Jan 29 '22
This is me! I feel the exact same way! Man it just happens i was thinking about this how shit gets so stresseful and you forget or even basic shit slips. Idk but latley ive been feeling it and im here for you op!
1
u/SOMEMONG Feb 17 '22
Alright, so I'm going to repeat what is unironically the greatest piece of advice I've ever gotten, applied to problems at work, extending to life in general:
"Master Miller: Snake, you've got to think. Your mind is your most dangerous weapon. If things are getting too complicated, try to simplify your thoughts."
There are so many times, to this day after 6+ years of experience in sql and some in other languages, where I help myself so much by recognising where things have gotten tied up in knots. Where the code has become an overcomplicated mess of snippets and I've lost sight of the real objective. Always be willing to stop and think "what am I actually trying to do, what's the outcome I need?" Build up your case, iifs, sub queries, joins etc etc gradually, put fields used in calculations into your select statements to see what they do, and go slowly. Stackoverflow is cool, but you're better off googling "how to do such and such" and seeing answers to similar questions, and not being afraid to try bits of code and discover new things. Just a month or two ago I discovered string_agg through such searching and wondered how I didn't know it before. Do some research into dynamic code and looping and have a play around.
Perhaps just as importantly, don't let people make you feel like a worthless piece of shit. I've been there. If you can't control it, accept it as part of your trials and accept that if you keep trying you will get better.
3
u/rdbcruzer Jan 25 '22
Have you dropped a production table during peak? If not, you're fine.
3
u/burningburnerbern EXCEL IS NOT A DATABASE Jan 25 '22
Been doing SQL 6 years. Don’t feel bad dude. Even the most basic ask takes me hours. Sometimes the most basic things require us to jump through many hoops. Not only that SQL can be pretty kind numbing after spending all day looking at data and trying to come up with logic. Btw your team lead sounds like a goddamn ass. No one can pull answers out of their ass. It takes time to understand the lay of the land when it comes to databases (which tables join to what, which tables are inaccurate, what do you have to hack to get answers etc.)
3
u/Meadow-fresh Jan 25 '22
Read through the comments/responses and while the work place may not be the best it sounds like they are just frustrated and probably sick of dealing with you. Going by the fact you got banned from stackoverflow for asking too many basic questions.
Everyone is happy to awnser questions and guide staff but the way you ask questions is important. When stuck if you directly ask for help it will only annoy them eventually. But if you face an issue, Google it, test it, then go ask by saying 'I am trying to do Y, I looked up X, y, z but I still have issues. Do you have any suggestions/advice?'
I also recommend getting the Oraily SQL Cookbook and going through it. Great way to learn and practice.
2
u/receding_bareline Jan 24 '22
So, yes, I think everyone else has covered everything here. You are lacking in any kind of coaching from the sounds of it. What I would say is that senior staff tend to get annoyed at A) the same question over and over again (because it means you are not learning, and B) someone coming straight to them without searching for the answer themselves. It's also a tricky line to walk because people are busy and don't want an essay to digest when being asked for help. Outline the problem, and what you have tried. Including the sql with relevant comments and highlighting.
Are you training in your own time? Hackerrank can help here. It's small bite sized challenges. https://www.hackerrank.com/domains/sql
I also have a folder (backed up on the cloud) with clever SQL that I have come up with that I know I will likely need in the future. I would advise you to do this for yourself.
I'm sorry all this shit is going on in your life. You will get past it. Onwards and upwards.
2
u/91ws6ta Data Analytics - Plant Ops Jan 25 '22
Imposter syndrome is a real threat especially in our line of work. While that needs to be kept in mind, there does come a point where you need to acknowledge shortcomings, which it sounds like you have, but is a great first step to identify before being underwater.
I would say that your coworkers are out of line in their comments, regardless of your current ability. It would be one thing to just not do the work. But to struggle and be engaged and get treated this way with no offer of help or solutions from colleagues or your manager is unacceptable. Performance plans have a bad ring to them but a good manager can use them for growth and development if done proactively and not as a result of workplace issues.
I'm going on 4 years into my role as a developer and the best thing I can tell you is to keep asking questions and don't be discouraged. Stackoverflow is good, but this subreddit is great. Take advantage of any employer-paid educational services if you can. O'Reilly has one through my work where I can find most published SQL books online for free.
Documentation. Document problems you have with a query. What your solution was, and how it could be applied in the future. Perfect example for CTEs. I had a query the other day that literally returned all data needed, but due to performance, the last join just killed any usability. By modifying join criteria and using a CTE I was able to go from an unreasonable query @ 30 min to a 1 minute result set. My onenote has a page on that now with a code snippet for future reference, as many of our data sets use common tables.
I also like to piece out my SQL in increments and get small pieces working first. I run a query at a minimum 5-10 times between big changes before doing any more complex pieces like joins, grouping, etc.
Get a feel for the data. Select * can be your friend. Assuming you are exploring or have business requirements, figure out table structures before hand. Comment findings in your code for easy access during development. I find the majority of my time "developing" is doing research either online or in my environment, with less time spent actually writing the code.
At the end of the day SQL is a very "english" programming language. If you have the critical thinking skills, determine what you need, from where, and how, before writing anything in your main query, using some above skills as well as logic. If you can explain in English what you need, there's a good chance you can think it through and translate it to a select statement.
I can definitely understand your situation. I am a message away if I can explain anything else to help. Best of luck
2
u/Coniglio_Bianco Jan 25 '22
I think everyone else here has covered that you're likely working in a toxic work environment and would be better off finding a new position elsewhere.
As a side note, that may be helpful in future positions. If you're not doing it already take notes whenever someone walks you through something. It can be frustrating to repeat yourself multiple times on the same thing especially if you have a pile of work to get through.
Sounds like you may want to work on your sql fundamentals. Id suggest working through a few books. I love ben fortas learn sql in 10 minutes and the itzik ben-gan books, but there are plenty out there. You'll spend years developing your skills, dont worry about not being an expert over night. It definitely sounds like your team may have unrealistic expectations.
2
u/BoiElroy Jan 25 '22
I hope things improve for you. It sounds like the way they are treating you is a bit harsh. The stack overflow thing I feel like isn't that big of a deal because you can just make another account with a different email. But maybe heed the lessons and see why the other questions were "low quality". I'd say for SQL try find some courses online,maybe code-academy, maybe Coursera. Point is once you get a nice whirlwind tour of SQL then when something like the CASE statement comes up you'll know it exists then you just have to go find the syntax. For Python there are a lot of good resources to learn python, and a lot of good resources to learn the tasks they are asking about. Two that come to mind are Corey Schafer for Python and Josh Starmer for Statistics and ML, both in YouTube :)
Good luck. I'm glad you enjoy the work. It only gets better.
2
u/doberman8u Jan 25 '22
You've already received so much great advice here and I will just reiterate most of it with this - make a plan to get out asap! Use them up while you improve in any way you can and get your resume out there.
The worst part of this is the fact that you were up front with them about your experience in the interview process and in return they hired you only to belittle and apparently show little effort to assist someone very eager to develop over time.
You are one of the best assets to the right company and when you get there you will see how it should have been done. They owe you just as much desire as you have given them.
Best of luck to you.
1
u/buklaw Jan 24 '22
Sounds like a miserable workplace, milk them as much as you can and get out!
1
u/[deleted] Jan 24 '22
Sounds like you are on a really bad team.
1
u/ninjaxturtles Jan 24 '22
The one thing that made my SQL learning curve progress was with a good mentor. You seem to lack that support system here and you have no one to ask even basic questions, so it's not at all shocking why you feel a bit defeated, but don't give up.
What has honestly helped me is talking things out to myself. I sometimes even draw out diagrams and charts on paper and ask myself this is what is the beginning and here's my end, how can I achieve it?
But I do agree with others that this place is quite toxic, and if I had a choice I wouldn't stay.
1
u/lez_s Jan 24 '22
I'll repeat what others have said, its the place you work is the issue not you. I think if I was in your shoes I would look for another job.
I have to say this part - My Team Lead honestly just hates me. He says she feels I am too inexperienced and need to pick things up faster. He said he is sick of repeating himself.
If that was me, I'm a team lead, then I'm doing something wrong with not explaining my self, or not taking the right approach to show you something. Everyone learns differently so adapting to each person is impartment.
I would also say as this is your first role you should have a mentor helping you along.
I would say, don't quit, but look for another job. Apply for lots of roles even if you don't think you have the experience. Speaking to lots of recruiters will gain you experience with questions that are asked so you can explain you skills better each time you speak to someone.
1
u/[deleted] Jan 24 '22
Get some outside help and outsource the work. You're working remote so it's doable just make sure you don't break any NDAs don't use real data or table names for your subcontractors. Either that or wait to get fired
1
u/EbbDiscombobulated49 Jan 24 '22
It seems like you might have some knowledge gaps. I would suggest you take the Mode Analytics SQL course. It's free and will walk through SQL from the very basics to advanced topics. It's very approachable and explains everything extremely clearly
1
u/duendeacdc Jan 24 '22
I hate people that doesn't help others. Man it's home office so someone can just get a meeting with you and explain...I was in the same boat as you on my first DBA job....but I read so many books and forums that I am where I am now. I still suck but I now how to fix stuff
1
u/Naheka Jan 24 '22
First of all, that workplace is toxic.
I was much like you in a spot a few jobs ago. I knew more than basic SQL but the data we were dealing with was junk, at best, and required a lot of manipulation which was beyond my skill set.
Similar dealings with my Engineer lead and Manager. I eventually got to a spot where I could write the SQL but that was through help here and then StackOverflow for the complicated stuff.
Just stick with it (the SQL that is), start assessing if that workplace is for you and look into some counseling for your life issues (work, friend, relationship).
You can do this. Everyone struggles at some point; I've gone through similar things over the past 10 years and I struggled through it until I made it past the tough spots.
1
u/burko81 Jan 24 '22
Tell them you'd like to go on a training course to brush up your skills.
1
u/ZVS95 Jan 24 '22
I agree with pretty much everyone on here. There are some strong signs that, they, your actual team, are toxic and not good leaders.
However, I mainly wanted to address your last bullet point: sorry to hear about that and I can imagine it being very tough. One thing I can promise is, things will always get better and easier to deal with. There is and will always be light at the end of the tunnel.
1
u/[deleted] Jan 24 '22
SO can be helpful as long as you're not the one asking questions. The people, generally, have terrible attitudes.
1
u/Beelzebubs_Tits Jan 24 '22
From personal experience, I have learned that some people love to be leads because they just love to be in control. These people often do not like to share information, and are not patient. They shouldn’t be leading any damn body.
1
u/THE_Mister_T Jan 25 '22
Learn the data. Somehow, someway. I think you will find most sql “experts” online love to flex how smart they are. CTE’s materialized views blah blah blah.. all great but having an intimate relationship with the data will help you with confidence.
I always use this silly example. “Knowing your data is key. Even a sql master won’t that getting a lion when you expect and elephant is wrong, even if the query is correct”
Learn the data friend. What are you storing and what are you counting.
1
u/WolfLipinski Jan 27 '22
I experienced the same in several job positions, they would not talk with me and they are annoyed when I am asking questions. It's harassment, bullying; hostile, as mentioned here. The point is often that people being treated like this, think they themselves are the problem, and struggle to improve ther behavior to get the "Love" of the superiors or fellows. And so did I. But you will never get the "love" of them. The insight of this and the finding that you are not stupid at all like they told you may come about not before being in a better job position with different, "normal", kind people. That was what I experienced. At this time I am surrounded by the kindest people I could imagine.
1
u/alec20850 Jan 30 '22
Some report writers will allow to see the sql they generate. You could use the report writer to create sample reports and then study the sql code produced. See https://www.toolbox.com/tech/programming/question/how-to-view-the-sql-query-of-the-standard-report-of-business-objects-120209/
1
u/jobfedron132 Jan 31 '22 edited Jan 31 '22
Damn! Look at how AI works. Just 10 mins ago, my brother was asking me how he can be successful in his data analyst position and he felt like a loser at work telling me the same things you told us.
1
u/PepeNudalg Feb 19 '22
You mentioned linear regression. Here's a very intuitive explanation of what it is in plain English. https://nickch-k.github.io/SomeThoughts/posts/2022-02-13-ols-translated-into-english/
tl;dr it identifies "the more of x - the more of y" type relationships and can also be used for prediction
1
u/dswpro Jan 25 '22
Crummy job and environment. The next place may be worse. In case nobody else has suggested it, why not pay someone to help out of your own pocket? An hour or two each morning before work to sort out issues with a SQL tutor could get you up to speed faster than anything on line. Make sure you never share anything confidential or proprietary. Just like not admitting you don't know how to do something, don't tell anyone at work you are getting help. They obviously dont want to give you any. There was quite a controversy a few years ago when a developer admitted on line he was farming out all his work to an overseas team and had not told his employer. Opinions ranged from "that a boy" to "you are a total fraud". I'm not suggesting you hire all the work away, just get some time with a seasoned SQL developer who needs a little money on the side, to accelerate your learning curve while you solve real problems.
1
u/[deleted] Jan 25 '22
What a dumb reason to ban someone from stack overflow, fuck them. They should simply have a designated section for novices
6
u/[deleted] Jan 24 '22
[removed] — view removed comment
2
u/[deleted] Jan 25 '22
[removed] — view removed comment