I have a keyboard with GMK firmware. This is fairly easy to do. In combination with layers, my hands don't have to move around as much. Easier on the tendons and possibly faster.
Yes. I have thought about this a lot. There are cycles...
Like thin client (VT100), to thick (client/server desktop app), to thin (browser), etc.
Similarly, console apps (respond to a single request in a loop), to event-driven GUI apps, to HTTP apps that just respond to a simple request, back to event-driven JS apps.
It depends on how you define the boundaries, but history rhymes.
I've certainly been keeping my eyes open for a MacBook Pro alternative. On my last time looking, I thought I'd try to find something with:
- retina-like resolution 15" screen
- 32GB RAM
- slim and light without a flimsy plastic case
- good battery life
- good trackpad
- keyboard home row centred
I could not find anything. I couldn't even find something with the first three items.
For some reason (bad software support? tradition?) the PC laptop market seems to simply not care that much about extremely high resolution displays. There are some, but none in systems with the overall build quality of a MBP.
I could get the retina screen with 16GB RAM, or 32GB RAM with a lower res screen. It was a few months back, so hopefully that has changed. I'm no longer looking though.
I actually prefer w3 schools to MDN. If I accidentally click on an MDN link it confuses me for a few seconds before I realize what happened and navigate back to w3.
By extension - the best SEO guide is almost certainly the first listing for 'SEO guide' on google.
Only if you can assume that they followed their own guide. I could see an SEO company posting a fake guide to make their own techniques more effective relative to any competition using that guide.
Right, so did I, and people were using it in production in 2015, but the first release was in late 2016 so you were using a testing version or used it late in the year. So this site rounded down from a little over 2 years from the first release. I imagine many of these dates would change depending on how you're defining when the technology first existed. And I remember how there was a sentiment that Google should just officially release the thing and there were worries about how the project might just be limping along and that could discourage one from adopting it if the project was going to be abandoned. But if the original commenter was just saying you could get an early version of it more than 2 years ago then it doesn't seem like that interesting of a comment and it doesn't justify the tone.
I remember looking for a house to rent in Mexico and wondering why some places seemed to be much more expensive than similar properties. Took me a little while to figure out why ;)
I had a small company that did software consulting work for one of the provinces. Around 10+ years ago governments started requesting "off the shelf" solutions instead of custom-developed software. This led to a situation where they didn't own the code, were tied to vendor upgrade schedules, and had to pay a premium for customizations. This had the result of spiralling costs.
Each time there's a scandal, they tighten the rules so that ultimately only large companies with teams dedicated to writing proposals can compete.
To be fair:
- we worked on smaller projects of a scope where one person could maintain a mental model of the system
- nothing so mission critical as payroll
I expect the pendulum to swing back toward more internal development and greater ownership and autonomy. So far, not much has changed.
I do notice that while I can't keep the 30th API I've used in my head for instant recall, I am much faster at finding the big picture. I'm a big fan of diverse teams. A younger programmer can just plow ahead without my careful consideration, but that helps keep me from stagnation. Similarly, I can contribute the big picture stuff to make the long term smoother and reduce technical debt.
I haven't seen brain.fm, but there's so many tools that can help me improve the way I work.
