The Day by day Developer.

Json can be a great pain in the memory:) .I've worked with JSON files up to 4 GB ,and believe me ,regular text editors start overflowing ,its like the whole PC gets frozen on JSON ,like its importing data not just loading it . It took me a good day about 18 hrs to figure out there is a great json viewer ,and guess what its called ,"JSON viewer" Except that its made by MiTeC .so its called MiTeC  JSON viewer . It loads the script not in a text editor but just a neat and dev friendly environment ,you can see distinctly icons that differentiate between the super objects blocks ,elements and attributes. It also doesn't deny you from looking at in neat text if you want to copy it without editing ,and still it doesn't lag a second. Now it also has an editor button, if you press it ,it will take some time to show the text but it isn't an awful amount of time ,I've hidden some of the JSON info here as it was for a critical client ,so don't worr

My coding setup Optimized coding setup As you see I prefer ambient lighting ,as dual monitors can blind you over time or cause you to live in an alternate universe.Using dual monitors is a life saver ,specially when you have this old raged core 2 due PC that you cannot gain anything from by selling .You can just use it for browsing taking off some good ram off  ,as well as saving some code resources and other programs that aren't the IDE or antivirus,except games of-course ☹️ . So how can this happen ?.How can the IDE cook without stack-overflow ? .How can fil;)es be transferred from one pc to another without using some messenger app And the solution developer ladies and gentlemen  is ..... "Input director". Link Its  very simple app ,you just download it on both PC's and it magically works on both as one PC ,you can transfer files by dragging ! and copy text effortlessly ,using the laptop you are working on ,you can also type on one l

Testers can be a great bug inside the developer's head .Vis-versa is also true ,there is no reason why people should lose their friendship because of code .The code needs to be regarded as a separate entity that doesn't belong to the developer.The dev has to tell the tester ,"Man this code has its own personality ,its like an artificial intelligence thing you know ".This is the first step because testers think the developers are doing it on purpose ,like they know the problem but don't think right because regression is always there.Or because the dev is a lazy coke addict . Devs also have a paradigm about testers ,they think testers are always seeking to find their bugs not only in code which some devs consider their property but in the dev himself .They think the tester is a spoiled brat who nags about the existence of a red asterisk or a stylish title in the middle of the night,not knowing the amount of hard work that was necessary for more important stuff