Love Foundation (6) and integrated it into a major overhauled manufacturer website recently, with Kentico Enterprise. In the very beginning of the overhaul, we used Orbit (5) for the product page slider and realized it had some issues that caused some headaches (we got it to work cross-browser however). Ultimately we switched to the recommended slick slider. It's great, but I noticed Oribit is still documented under v6 Foundation. Is it being supported again?

For me, my company provides a never ending supply of coffee, various nuts, apples and bananas. But besides regular coffee always on tap, we have an in-house cafe with most beverages you could see at a Starbucks or Dutch Bros. Pretty talented baristas. :)

I have used VS exclusively for years, so I use // TODO: comments to keep a list of areas to look at refactoring later, fix (I may be on a different item at that moment and don't want to lose focus), etc. Todo comments have also helped me diagnose a few problems recently, where a past developer had planned on optimizing a function and never go to it, and it was time. It merely helped me see an area of concern that's carried on, where he simply said // TODO: this could be an issue eventually .

I've had quite a few in the last 5 years, as I was never impressed or comfortable. I now have an 13" HP Spectre with 8 gigs of Ram, 256SSD and i7. It is an amazing machine considering it's small and a convertible tablet. At my office I use a Dell Latitude (company issued) with an i7 and 256SSD. The SSD and late gen i7, at a minimum, have been the way to go for me.

I used to want one, until I got the HP Spectra. I also realized (and was told) that the MS Surfaces are way overpriced considering you can get the same and more (convertible, pen, etc, etc) from other makers.

I think there are two funnels to this- 1) You want to learn it for yourself (Online Tuts) 2) You have to learn it for your project (Documentation/Reference) For me, Tutorials are awesome across the board to see someone who's experienced speak to their real-world examples and concepts that you might not have thought of. Gives insight to possible best practices and "gotchas". On the other side, you might have a particular project where you have a roadmap, specs, etc, and can get right into the Documentation to accomplish it. In most cases, I'm doing both #1 and #2 above.

I need to dive into Ruby... seems to be popular again. The only thing about Tutorials that I personally like, are that it gives examples ( usually ) from a person that already has been experienced and it really boosts your overall concept of what you can do, best practices (they've picked up), etc.

1) Hashnode.com 2) Stackoverflow.com (Sections: Web Applications, Server Fault, Webmasters, etc) 3) Pluralsight.com 4) MSDN (I.e., https://channel9.msdn.com/) 5) Reddit.com (mostly /web_dev and frontpage) 6) Htmlreference.io & Cssreference.io 7) Twitter.com (Catch numerous individual thought-leader posts) 8) Youtube.com (Subbed channels or I go down rabbit hole of related videos) 9) C-SharpCorner.com 10) Forums.Asp.net

I search the web frantically looking for that magic piece of code, to fix what I broke by doing a search frantically on the web, looking for that magic piece of code.

@Anirudh Sylendranath, I prefer "offense" ;) Sorry, had to. Carry on...