Now you know you don’t know
This week I’ve learned everything I need to know to get a job in the data area, I consider that knowing what you don’t know is just as important in your learning path as you already mastered since you can and should add these topics to your study if is that you want to be able to improve yourself in the short term.
Well, I’ve learned that although I’m not exactly new to SQL, I still have a long way to go to master this declarative programming language (That is, you just have to tell it what you want it to do and the language will do it, you don’t have to worry about how. You want it to sort a series of elements in alphabetical order, it does so without any problem, although of course, it will not ask you by which method it should do it and this may lead to some more advanced problems that it is not convenient to talk about at this time).
I also learned that I’m very slow to program, although it’s true that I’ve an acceptable algorithm resolution, it’s also true that I lack practice and that means that when implementing the solution that I outlined, I do it with more time than I‘ve in the interviews.
I would also like to say that I’ve learned to think about the possible scenarios that a problem represents, I usually think of edge cases, which is to devise a solution not only for what is in front of you but also for the largest number of cases, that is to say, what happens if in a problem designed to handle collections of numerical data you enter letters, what would happen if you do not enter anything at all or if you enter a gigantic numerical data. Taking these cases into account from the beginning represents not only a better understanding of what you’re doing, but also that in the future you’ll save time since these cases where you’re presented with atypical situations are just that, atypical and therefore they hardly happen but it is It is possible that they happen and for that mere fact it is worth considering them since if there’s no planning of what to do when they happen, it will lead to problems that will be difficult to solve, especially if the work of other people depends on yours. Believe me, fixing something like this is very difficult in terms of money and time, the less time you spend fixing bugs that could be fixed with better planning, the better.
