Nothing here yet.
Nothing here yet.
No blogs yet.
I have used code time & I can assure that it has burned me out by showing how many actual hours I was coding. It has some metrics it considers as coding time. For example, if I am looking at a problem thinking about it after opening my editor, then after 10 seconds(or some threshold) of inactivity, it assumes I am not coding until I hit a key. So, it might be a good metrics collector for beginners who're interested in trying to do lot of things. But if you're someone who's actively in a TL/Senior role, it will make you feel bad. I am not against codetime/any other tools that show these metrics. Instead, I believe in the fact that developer productivity is better when we understand we & people who employ us trust us and know that we're doing a great job. Just a little human side from all the Tech bloat that happens around.
I am a fan of dark mode. However, when I am reading articles I think white would be great when I am not reading plain text. I think so because, I ,may be most people, are tend to understand more from pictures than plain text and since Hashnode is a place with text and images I think dark mode would kill the way images look. So, I don't personally prefer dark mode for articles. :) However, that would be a welcome addition when I am just reading plain text. Great work guys. Cheers :)
Looks like I have the smallest list. I had a little knowledge of C/Java before I started working. However, these are the things I have learnt: Java SQL Javascript HTML Typescript Python (for personal learning though)
I would say, trying to learn every single thing and thinking to become the best in all of those one day. I was a simple fresher, simple because I was just a blank fresher with a decent logical sense and able to code in C language to a decent level and a bit of core java(not HTML, no javascript, no CSS etc because I hated UI/UX). However, I have started to learn java(java EE probably) for my project. I tried to learn everything that the brilliant architect of our project has designed. And I ended up learning everything in pieces. I have become so immersed in that that I ended up reading lot of time and trying stupid things and finally understood that I've take too much already. Take it one at a time. I became the goto for anyone even the seniors if they wanted to know of something. In the end, the project ended and all my knowledge was left with me with little use. This time it was javascript. This time I was careful, I started doing little things. When I felt, I need something for doing it better, I started learning again. Slowly, the beast to learn everything was back and ended up reading almost everything on medium and even, the tc-39. I was initially a guy who was very much against UI/UX and at this stage I understood that it was just different and not a nightmare. Now, after almost 4 years being a professional developer, I understood that I need to understand how to solve a problem properly than learn a language. However, it is important to apply language specific optimisations which could make your code faster. So, trying to learn too much is my problem. I can say, j has a great point which I will be planning to do next time when I want to solve something but that next time is never coming though. Cheers :)
1) I agree with Ujjwal Kanth . That was one of the most stupid mistakes in regards to programming that I have done. However, it's good till an extent when you are ready to check on the other ways to solve the same problem and make it and yourself better. For example, if you are trying to solve a computationally expensive prime number generation problem, you'll come up with a simple solution with your plain brain. That would be great, implement it and then you'll see that it can be improved. If you miss this step then you'll be extinct soon. 2) Other would be trying to make it look modular, performant, premature optimization and following all standards. Because, as said earlier, the process of learning is lost and many edge cases will be lost when we try to make it very standardized code and fixing those it becomes dirty which is too bad. 3) Also, learning a new language without considering it's reason for creation. Anyone would learn by starting to code, but there's a small issue here. For example, I know java and I am learning python by solving a problem. In java I need to store data in a format to reverse it and all. If I'm writing the same solution in python replacing the syntax, it's as good as not learning python. Because, I am trying to port a program here. I might even miss simple ways of string manipulation in python which could be much faster ( It may look funny, but it matters when you solve computationally heavy problems like in https://projecteuler.net/ ). Because, for some problems some languages offer better solutions than others (just my personal opinion though. I am not starting any language wars :J) 4) Considering too much about design patterns, data structures when you're learning a programming language. This might even make you loose the motivation. Looks like I have given points which even contradict within themselves. Let me know if you find any mistakes. Cheers :)
If you are using some way to read data from a local file. Then just read it using this method. 1) I would expect you to be using some build system like webpack or browserify or something of that sort. You can probably tweak that a bit to accept reading of json files as well and just get that file using the ES5 stlye require or ES6 way using import . 2) Else, if you want to read it over streams or something like that try using the fs from node. Cheers Hope this helps :)
Following a coding style guide, could be your own or of the organization you work for. Also, making sure it's easy to read the code, there by tracking down bugs would be easy. I say tracking down because, I know bugs are meant to be there in any code, at least when coded by a developer like me, it's better to have a simpler code that performs little slower than a very robust code that is very fast and difficult to understand in case of any bugs. Because in my experience, bad variable names cause more issues than a bad code does. Also trying to make the code align with latest standards and design patterns.