cleaver

How on earth would you monetize to get a reasonable return on that size of investment?

I recall a similar statement from Ed Yourdon in one of his books (90's?)

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.

That's what I found. Another pet peeve was extremely wide screens, although we don't see that as much these days. Not great for editing text or code.

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.

Other than that, the XPS15 was a front runner.

Everybody has used them, but nobody wants to admit it ;)

I for one, would like to know who does their SEO... they are often at the top of the results for many searches.

[flagged]

"Angular has been out for 2 years" Oh?

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 ;)

Having cut my teeth on Turbo Pascal 3, I quickly adopted Joe when I started using Linux around 1995. Most of the same key mappings were there.

I'm a bit surprised to see it still is around. I eventually switched to vi, since it was reliably available on most systems.

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.