razorfen

4 ms·

1.
by razorfen 7mo ago
Their new appointment of leader for their Xbox group suggests that they intend to wind down that business unit in time. The founder of the Xbox team has commented that he believes it’s the beginning of the end for Xbox, for the exact reason
2.
by razorfen 1y ago
This has become a personal debate for me recently, ever since I learned that there are several software luminaries who eschew debuggers (the equivalent of taking an oscilliscope probe to a piece of electronics). I’ve always fallen on the si
3.
by razorfen 1y ago
Can anyone explain how they maintain backwards compatibility on formats like this when adding features? I assume there are byte ranges managed in the format, but with things like compression, wouldn’t compressed images be unrenderable on cl
4.
by razorfen 3y ago
> phishing resistance (with UX that supports that) and low-level security audits of encryption software and hardware Pardon my ignorance, but isn’t this saying “we can’t rely on reducing the likelihood of breaches, we should focus on red
5.
by razorfen 4y ago
> Also the code should be written "for the now", not for "that future feature it would be awesome to have someday like making it compatible with every other library X, etc.". The folksy software adage for this is YAGN
6.
by razorfen 5y ago
Phoenix is robbing Peter to pay Paul with regards to water. Phoenix survives thanks to extreme planning measures and water diversion from the Colorado river, but that’s not going to be tenable in the next 30 yrs. There is almost no well or
7.
by razorfen 5y ago
Nor do they necessarily have the ability to do discretionary prioritization of certain bugs or features, even if they did see it.
8.
by razorfen 5y ago
You may not be in one job forever, and you can move between about 10,000 tech companies through a long career if you are in the Bay.
9.
by razorfen 5y ago
I don't completely disagree, but his point about the irrelevance of SOLID, OO, and Java in this supposedly grand new age of FP programming ignores that OO is still the pre-eminent paradigm for most applications and Java is remains one
10.
by razorfen 5y ago
It’s the first I’d heard of this axiom. Can you give an example of that in a real architecture? I think about a central server with multiple terminals on a network. There the node is the beefy boi and the terminals are just I/O devices
11.
by razorfen 5y ago
ITT: a non-controversial opinion shared by most programmers. Print debugging is fast in many cases and requires little mental overhead to get going. But for some/many systems, there's a huge startup and cooldown time for their app
12.
by razorfen 6y ago
Remember: "CTO" sometimes means "I am the technical founder of a 3 person company"
13.
by razorfen 6y ago
In the uuid case, the person had no choice. Remember, these are principles, not laws, and at some point your system is making concrete choices. Choosing UUIDs isn’t necessarily a OO design problem. He was just highlighting how expensive it
14.
by razorfen 6y ago
The public plaintext emails are not a good idea. Scrapers will gobble these up and spam those emails into oblivion. At least put them behind a captcha.