HNHacker News
TopNewBestAskShowJobs

urban_winter

254 karma · joined April 16, 2018

London-based software engineer.
submissionscomments
urban_winter··on Former University of Iowa hospital employee used fake identity for 35 years
> If I found out one of my coworkers was a career bank robber I'd just want to get a beer and hear the crazy stories.

Would you want to hear the crazy stories of a two decades ago child murderer too?

I didn't think so.

urban_winter··on A predicted quasicrystal is based on the 'einstein' tile known as the hat
Harry probably shouldn't feel so bad about the bug in the published listing.

I typed in plenty of games from computer mags in the 80s and they almost never worked first time. The problems were sometimes my errors (have you ever tried retyping 100s of lines of small-primt code?) and sometimes present in the published listings.

Whichever, the errors meant that reasonable debugging skills were necessary to get any of them working. It was good training.

urban_winter··on I fought the PayPal and I won
It's worth knowing that in the UK PayPal is covered by the Financial Ombudsman service. They wouldn't be interested in accounts being blocked as in this case but they were very helpful to me when PayPal made a payment that I did not authorize and then refused to put it right.

I don't use PayPal any more. Their support staff are impossibility hopeless so any kind of problem with your account will cause you a world of pain.

urban_winter··on C++ audio mixing library design
I wonder if, in retrospect, the decision to use floats was a good one. The author mentioned issues with the time of each sample for the sine wave, which were float-related. I get that audio effects (compresser, reverb etc) are probably easier using floats but I don't immediately see why it's better to have float as the core data structure and convert to int at the end rather than having int as the core and convert to/from float only when needed.
urban_winter··on We Put Half a Million Files in One Git Repository, Here’s What We Learned
What's the value of a monorepo if developers only ever check out a small subset of it? Wouldn't multiple repos allow greater scale without any practical reduction in utility?

For example, all the localisation files could live in a separate project (if we accept the need to commit them at all). Some tools would be needed to deal with the inevitable problem that developer working sets would not align with project boundaries, but that seems like an easier job than making git scale while maintaining response times.

urban_winter··on “What if it changes?”
"Copy code if it's used twice" is terrible advice. You are creating a landmine for future maintainers of your code (often yourself, of course). Someone will inevitably change only one of the two versions at some point in the future and then you're going to have to rely on tests to catch the issue - except that your tests will probably also reflect the duplication and you'll also forget to change the 2nd test.

The only possible justification for duplicating code would be that creating an appropriate abstraction is harder. Given that there are generally economies of testing when you factor out common code, that's usually just not true.

"Duplication is evil" is a more reliable mantra.

urban_winter··on Oxygen Candles: Providing Emergency Air
Exhaled air is about 17% oxygen, 4% carbon dioxide. So, as previous poster noted, scrubbing the CO2 is your first priority. You can't breathe air with greater than about 4% CO2 indefinitely. Oxygen levels lower than 15% are also bad.

Diving rebreathers are an interesting implementation of these rules in that they are lethal if you get it wrong.

urban_winter··on A first for Canada: New type of nuclear plant opening by 2028
Does anyone understand this? "Some of the main differences that the MMR has from conventional nuclear plants is that the reactor cannot meltdown as the heat is passively released into the environment..."

300MW is a lot of energy to passively release into the environment. Does this design really fail safe? And if so, how?

The Fukushima issues were caused (IIRC) by failure of the backup generators to run the cooling system after the reactors were shut down. Do these small reactors really not need any external power when in that state? And do they get into this state by default? I.e. do they shut themselves down without external power and if the control systems fail? That would seem to be a massive safety advantage if it's true.

I remember reading about UK magnox reactors where the graphite control rods were held above the core by electrically powered actuators and which were designed to fall into the core (and stop the reaction) if there was a power failure. Perhaps these reactors are similar.

urban_winter··on French fighter jet joy ride goes très, très wrong (2020)
When I worked at British Aerospace Dunsfold in the late 80s/early 90s, it was a hard rule that nobody got to sit on an ejector seat unless that had been training in its use. I am surprised that it's not an absolutely universal rule. The consequences of inadvertently triggering an ejection while in the maintenance hanger are pretty ugly.
urban_winter··on How to organize yourself as a solo founder
I've never found a way that I like to integrate dealing with email into a to-do list. Reading emails is a perpetual need but it is damaging to focus and I often find that it saps my energy by reminding me of all the things that are not yet done. I've tried having fixed times of the day where I always deal with emails; adding "30 minutes of email" to my task list; reading them between each switch of tasks. None of these approaches really cracked it for me. I haven't read "Getting Things Done" - I wonder whether it has a solution.
urban_winter··on Best practices can slow your application down
An obvious question is whether the focus on performance first is correlated with the success of stack overflow. If the same level of succes could have been achieved without squeezing as much performance out of each server then the sacrifice of testability is a dubious one.

The article doesn't explain why horizontal scalability wasn't pursued instead of their approach of performance efficiency (i.e. greater performance from a given amount of resource). It's certainly true that at the time that SO was starting, scaling horizontally required far more handbuilt tooling than it does today but it certainly was already a widely used pattern. The likely reason is cost, but that then comes back to the first question - would SO have been equally successful if it had higher infrastructure costs in its early days?

The persuit of efficient performance at the cost of aspects of quality (of which testability is only one) can only be justified if efficient performance is truly necessary for success. A much smarter person than me warned against premature optimisation. That seems relevant here.

urban_winter··on An oral history of Bank Python
Yes. Many adverts will specify financial services experience but it's worth applying anyway. You'll probably find that roles in back-office technology areas (operations, finance etc) are less demanding in this respect. I hired mostly from outside the financial services industry because other industries had, on average, better-skilled developers, lower salaries and better development practices.
urban_winter··on An oral history of Bank Python
BAML Quartz was conceived by a bunch of front-office quants who had not the first idea about the software needs of a big bank beyond the front office. There was an arrogant assumption that front office software is obviously the most complicated/difficult variety of software within a bank and therefore any system designed with front office requirements at the forefront would, of course, be perfect for universal use.

This assumption was challenged at the time by various groups - I was closest to the Equities Operations software team (although not part of it) who absolutely dug in their heels and refused to use Quartz. The assumption was explosively invalidated when people started implementing in Quartz applications that fell under Sarbanes/Oxley regulations and Quartz picked up a severity 1 audit finding - because Quartz was explicitly designed for "Hyper Agility" (literal quote from the quartz docs) - and anyone-can-change-anything-at-any-time does not make for applications that the regulators trust.

There was an interesting trajectory of Python hiring during my time at BAML. I joined just as Quartz was getting started and we managed to easily hire tens of python devs in London because it was easy to sell the fact that BAML was making a strategic investment in Python and therefore their (at the time relatively uncommon) skills would be highly valued. But as Quartz matured, Python developers generally came to dislike it (for reasons see original article) and it became hard to retain the best ones. And after a while Python 2.x became a massive embarrassment and, as Python became a more common skill in the marketplace, it became harder to hire good developers into BAML.

urban_winter··on Why is everyone a bank?
That is profoundly untrue in my experience (13 years of working as a Dev manager at UBS and BofAML). The knowledge of how the business really works sits largely with the long-served IT and Operations staff. This is certainly the case in the back office (clearing and settlement) and in the regulatory space. I can't speak so much for the front office, but it seemed that the developers with successful careers were those who understood the business and therefore could talk to traders and desk heads in their own language (far more successful than the developers who were actually any good at producing maintainable software, but that's a different rant).

There are lots of things wrong with technology in large banks but the business knowledge of developers is pretty low on the list.

I left banking a few months ago, so I am no apologist for the sector.

urban_winter··on We Need to Dream Bigger Than Bike Lanes
The UV issue is a red herring. There are many reasons why people need to be outside and cycling is only one of them. UV is a manageable problem for walkers and outdoor workers, cyclists are not a special case.

I guess that you've never been on a bike on a very hot day. It's much, much more pleasant to be ventilated by your self-created airflow on a bike than it is to to have sweat pouring down your back as you walk around.

urban_winter··on Lockheed has an opening for engineers with VAX experience for the F22
I started my career working for British Aerospace in 1989. We used VAX/VMS as our development platform (Code was CORAL 66 and then ADA). I spent some time supporting the Sea Harrier flight test operations - so I would have fitted this job perfectly about 28 years ago!).

I'd like to say that I'm astonished that modern aircraft still use the 1553 bus, but nothing surprises me when it comes to the use of stone-age tech in military hardware. For example, the other Harrier I worked on in the early 90s (GR-7 - same as US AV8B) still used core memory.

urban_winter··on Autonomous braking: 'The most significant development since the safety belt'
The BBC story, also reported in multiple other places, is a nice bit of Volvo marketing g, but is nonsense.

Volvo introduced Aeb in 2007 on the XC60. The XC90 only got it when they introduced the new generation a few years ago. Therefore claiming that the exceptional safety record of the XC90 is in any way related to AEB is just rubbish.

The reason why XC90s are associated with so few passenger injuries (note, no claims are made for injuries to other road users by XC90s) is that they are large, heavy and chosen by safsr-than-average demographics.

← PreviousPage 2 of 2