rvalue

This is ridiculous! Is there no other way to test features on OSX ? or like a cloud environment?

Not only is this waste of money but also non eco friendly buying all that hardware

Writing an implementation for parallel Travelling Salesman Problem w/ B&B using MPI and getting some god damn speedup

Any chance the project was called Lazarus? :D

I transform every chapter to some piece of code, either one already in it or of my own. If the chapter is only explaining the fundamentals of something, i make separate yellow notes in my study for a quick concept look.

If I don't understand something at all, i usually search for code samples in Github someone might have used or look for questions related to it on stack overflow. This gives me a general idea if what i am learning is complicated stuff, or considered difficult or unused or is complete bullshit.

At the end, I implement something by taking pieces from all chapters, & keep that project for later reference.

Also, when I am learning about something which is more of a framework, I try to find reasons of why something is done like that, look into internal implementations without getting into much complexity so that if ever this framework support goes off, I know how to implement my own smaller version atleast

I am a slow reader and I don't like any disturbances so I pick the best time to learn something, probably night time.

I still find it shocking how people can continue to write in Go which still does not have an official debugger!

Good thought but this simply would not work for me. Lots of context switching and I simply don't see myself making so many notes

isnt TDD dead already ?

Just write unit and integration tests

thanks :)

I think there is some confusion here.

What i meant was applications should be self documenting, something like swagger comes to my mind.

I am completely with you with the idea of replicating the whole system locally with help of Vagrant and making sure it is as close to production and then start and stop stuff and observe the change

Intellij does a very good job for most of my programming and I use it daily.

In the process of learning a distributed system, the process of looking at the code as its documentation is not the ideal way. One could spend enormous amount of time to just understand a simple business usecase.

But then just because it takes time doesn't make it untrue.

I would rather accept a system which self documents itself with every change.

The point of breaking things is all well and good but to truly understand everything, after breaking also one needs to put the together one by one and understand their interactions so that if any one in the pool of modules fails, one knows what exactly would have caused it and how to be more resilient towards failures.

Thanks Stephn_R

I did not think anyone would take time to answer so many of my questions. I agree with you on lots of points you mentioned above. Regarding the documentation I usually trust it if the module or the system is new, but if its old enough, i assume its outdated, architectural drift exists and only take that as a reference of how the system was planned to be like.

This also gives a lot of use-cases to begin with and understand the control flow. Regarding test cases, integration and regression tests help a lot in finding failures but I feel more confident about them if written by the same developer as the original thought for the code change is more pure with him and the reviewer.

For knowledge tracking, I guess there is no easy way, one learns from experience and time, but it would be great if there were some great tools to capture thoughts and map them to a definite state in the application without making any change in the codebase.

I have been in my academics for 6 years doing my bachelors and masters and less than a year in my professional career. The sheer amount of stuff one needs to know about building scalable and distributed applications is just amazing and nerve-wracking at the same time and I will keep your secret in mind :)

For me, A full stack developer is some one who has knowledge of ML, Web Design w/ UX, Application Development for web and mobile, Databases and Big Data