Computer Science Field Guide

Post by talideon » Fri, Feb 05, 2016, 6:22 PM UTC

conceit wrote: post #47

talideon wrote: post #38

Earlier quoted context omitted.

There are, at least, things like Termux ( https://termux.com/ ), on Android. Just for laughs, I've been doing actual work (using git, vim, and Go) in Termux on my Nexus 10. Only two things got in my way: screen size and the inability to have a browser and terminal on screen at once. What's particularly sweet about Termux is that it has an APT-based package manager. Given the right tools, even something as locked down…

Windows had an msdos assembler preinstalled, last time I checked, which was before vista. Now the 16bit support was removed, but edge comes with a javascript engine, right?

Post by bastijn » Thu, Feb 11, 2016, 6:00 AM UTC

JoeAltmaier wrote: post #35

bastijn wrote: post #34

"YAGNI stands for “You ain’t gonna need it” and tells developers to keep things simple and only design and implement the things that you know you are really going to need. It can be tempting to think that in the future you might need feature x and so you may as well already create it now. But remember that requirements are likely to change so chances are that you won’t need it after all." [0] I work in a platform tea…

I was with you until the parenthetical remark, which seems to contradict the point. Platform software is great for getting 80% of the way there; then you can be screwed. My last company threw away our expensive IP and tried to use off-the-shelf platform stuff. They're struggling now, with a product lacking features, performance and scalability. Funny, that's what the platform promised to deliver!