• 0 Posts
  • 26 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle
  • Many, many years ago I used to have two Wyse50 terminals, running split screens each with two parts. I did a lot of support on remote systems (via modem!) and I would have a session on a customer system, source code and running on our test system and internal stuff. I didn’t have space for a third terminal.

    At another job I had an office with a “U” shaped desk. I would spread printouts across half the “U” and swivel around between the computer and the printouts.






  • That used to be really true when I was a kid in the 79’s, but not so much today. Back then, a quality guitar cost way more than the cheap stuff and the cheap stuff was rubbish.

    Nowadays, with CNC machines everywhere, there are lots of modestly priced guitars that are very playable. The junk that we used to have to settle with back in the day only exists in the realm of “toy” instruments that almost aren’t intended to be played.

    Seriously, $300 can get you a very playable instrument, especially in electric guitars.









  • Canadian providers all charge about $15 a day to “roam like home”. For about $20 I can buy a 30 day 5GB data only plan for Europe. Getting a European phone number doubles the cost as most of those plans have much more data as well. You can buy the plans before you leave, download and install the eSIM so you’re ready to go when you arrive.

    The wife and I both bought Pixel 7’s this year as they support eSIM. We’re in England right now. Our cost roaming would have been $600+. Only one of us needed a local phone number, and the has just data, and the cost was maybe $70.



  • I’m not sure that what developers really, really need is faster programming cycles. Most teams could benefit more by controlling the process - from idea to deployed. How much technical debt is incurred because users/customers can’t prioritize features or give accurate requirements, there’s way too much WIP, features are huge, releases are huge and infrequent and the feedback cycles are far too long.

    So yeah, as programmers it’s always cool to look at ways to program faster, but what’s the point in programming stuff nobody needs faster? Or programming the wrong things faster?

    I’d be willing to be that if you asked any team, “What are the biggest impediments to delivering value to your users faster?”, the answer would be that you can’t cut code fast enough.