Had the Windows Insider Preview for a month or so to get Ubuntu Subsystem early back when it was Insider-only.

Turns out that your license policy changes when you use Preview builds: if your PC isn't updated to a certain build by checkpoints set throughout the year, your license expires and you have to reinstall Windows. No way to recover anything already on the device. So if you get Insider Preview and shut your laptop off for too long...

Thus began a killer combo attack on my Surface Pro 3.

While trying to figure out what was going on and loading up a recovery on a flash drive, the Surface Pro 3 BIOS was sitting idle behind me. On 100% CPU. The only reason I think this is that by the time I noticed the insane fan noise, the screen was hot enough to burn my finger as I tried to turn it off. The heat sensor triggered it to shut off before I could, though.

That heat sensor, however, won't turn it off if it's busy installing Windows, supposedly to keep anything from getting hopelessly corrupted. What followed we're 3 hours of fan whirring from a slab of metal hot enough to cook an egg with.

Windows is back and working. The battery indicator, however, melted during reinstallation. And the battery lasts an hour, max. Thankfully I'm not out of a tablet, but it seems to me that W10 is becoming more and more like malware, just waiting for you to activate one of it's delightful payloads.

Games which have a save point or checkpoint system: FUCK YOU!

This is a technical limitation that was present in game consoles in the 90s.

There is no fucking need to implement save points in games made today!

It serves no purpose other than to generate frustration for the player and make the player redo the same section of the game again and again when he fails.
Oh how much fun it is to repeat 20 minutes of tedious shit as a punishment because I fell into your cheap trap and died!

And even if I don‘t fail, I want to be able to stop the game at any time and continue later where I left off. Is that too much to ask?

I don‘t want to be forced to progress in the game until you decide that NOW, after 20 minutes is the time that I am allowed to quit playing.

This is a fucking design decision. Don’t make your design suck to imitate the games from the past that did it for technical reasons!

Having a lot of bad experiences while working as intern in startups and about to join a MNC, i wanted to share my work life balance and technical demands that i expect from a company. These are going to be my list of checkpoints that i look forward , let me know which of them are way too unrealistic. also add some of yours if i missed anything :

Work life balance demands ( As a fresher, i am just looking forward for 1a, 2a and 8, but as my experience and expertise grows, i am looking forward for all 10. Would i be right to expect them? ):

1a 8 hr/day. 1b 9h/day
2a 5days/week. 2b 6 days/week
3 work from home (if am not working on something that requires my office presence)
4 get out of office whenever i feel like i am done for the day
5 near to home/ office cab service
6 office food/gym service
7 mac book for working
8 2-4 paid leaves/month
9 paid overtime/work on a holiday
10.. visa sponsorship if outside india

Tech Demands (most of them would be gone when i am ready to loose my "fresher " tag, but during my time in internship, training i always wished if things happened this way):

1. I want to work as a fresher first, and fresher means a guy who will be doing more non tech works at first than going straight for code. For eg, if someone hires me in the app dev team, my first week task should be documenting the whole app code / piece of it and making the test cases, so that i can understand the environment/ the knowledge needed to work on it

2. Again before coding the real meaningful stuff for the main product, i feel i should be made to prepare for the libraries ,frameworks,etc used in the product. For eg if i don't know how a particular library ( say data binding) used in the app, i should be asked to make a mini project in 1-2 days using all the important aspects of data binding used in the project, to learn about it. The number of mini tasks and time to complete them should be given adequately , as it is only going to benefit the company once am proficient in that tech

3. Be specific in your tasks for the fresher. You don't want a half knowledgeable fresher/intern think on its own diverging from your main vision and coding it wrong. And the fresher is definitely not wrong for doing so , if you were vague on the first place.

4. most important. even when am saying am proficient , don't just take my word for it. FUCKIN REVIEW MY CODE!! Personally, I am a person who does a lot of testing on his code. Once i gave it to you, i believe that it has no possible issues and it would work in all possible cases. But if it isn't working then you should sit with me and we 2 should be looking, disccussing and debugging code, and not just me looking at the code repeatedly.

4. Don't be too hard on fresher for not doing it right. Sometimes the fresher might haven't researched so much , or you didn't told him the exact instructions but that doesn't mean you have the right to humiliate him or pressurize him

5. Let multiple people work on a same project. Sometimes its just not possible but whenever it is, as a senior one must let multiple freshers work on the same project. This gives a sense of mutual understanding and responsibility to them, they learn how to collaborate. Plus it reduces the burden/stress on a single guy and you will be eventually getting a better product faster

Am i wrong to demand those things? Would any company ever provide a learning and working environment the way i fantasize?