When I bought my laptop last year, I did it for the same reason :) Acer Aspire 3 w/ Intel Pentium 4417U/4GB RAM/Intel HD Graphics 610 iGPU/500GB HDD. This was the most I wanted out of my development machine, since it's an 8th Gen Intel CPU with all modern features and still dual core and cheap. Btw I'm a student, and not an actual developer.
I do want to study machine learning however, but for that a budget gaming laptop which costs 4 times more won't be much different from this one (because I can almost do the same stuff in this machine with some more patience) I have so I'm saving for the best laptop available.
I would like to point out that, others would've mentioned it too - working on a high end machine is not all that bad. In fact it can make the process easier for you because the main work can be done faster. Then test it on a lower end device and optimize there. That should yield the best results. :)
Then test it on a lower end device and optimize there. That should yield the best results. :)
No, unfortunately, this "trick" is not working at all. In such an arrangement, you will blame your test machine for being slow, not your code. "It is working well on my machine" is very common way of thinking.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
When I bought my laptop last year, I did it for the same reason :) Acer Aspire 3 w/ Intel Pentium 4417U/4GB RAM/Intel HD Graphics 610 iGPU/500GB HDD. This was the most I wanted out of my development machine, since it's an 8th Gen Intel CPU with all modern features and still dual core and cheap. Btw I'm a student, and not an actual developer.
I do want to study machine learning however, but for that a budget gaming laptop which costs 4 times more won't be much different from this one (because I can almost do the same stuff in this machine with some more patience) I have so I'm saving for the best laptop available.
I would like to point out that, others would've mentioned it too - working on a high end machine is not all that bad. In fact it can make the process easier for you because the main work can be done faster. Then test it on a lower end device and optimize there. That should yield the best results. :)
No, unfortunately, this "trick" is not working at all. In such an arrangement, you will blame your test machine for being slow, not your code. "It is working well on my machine" is very common way of thinking.