3 ms·
Banking is pretty desperate for talent, probably because no one wants to suffer the complexity of the problem domain. I showed someone the models we use to trac
by bob1029 5y ago
Banking is pretty desperate for talent, probably because no one wants to suffer the complexity of the problem domain. I showed someone the models we use to track a customer implementation and they thought we were insane for even thinking this is a good business to be in.
Because the problem domain of banking sucks so much, the tooling is necessarily simple and "unsexy". We like things that fit into a single VM/folder and can be built in 1 click. Anything more complex than this is almost certainly going to fail by default under the combined weight of unnecessary technical complexity and vast (and necessary) business requirements.
It took us until the 3rd year of integration with one of our banking customers before someone in IT even gave enough of a shit to naturally ask the question "so what language/framework/technique did you write <product name> in?" Obviously, we are required to disclose this in legal materials prior to implementing our product, but our customer sees "Microsoft" and rubber-stamps it without much drama. No one else gives a shit about the tech after this phase of the project (which lasts approximately 1 phone call).
- Nextgrid 5y ago> Banking is pretty desperate for talent The salaries don't suggest that, unless I'm at the wrong locations and/or looking at the wrong banks.
- bob1029 5y agoAllow me to clarify - You typically dont work directly for a bank as a software developer. You typically work for some vendor who sells software to the banks. We have many banks as our customers.
- eafkuor 5y ago> Banking is pretty desperate for talent, probably because no one wants to suffer the complexity of the problem domain I assume it's mostly because not many decent software developers want to suffer Banking's work environment
- xtracto 5y agoWhat do you mean? you don't enjoy having to cut all the red tape during a pull request to apease the SOC2, PCI, ISO27001, RGPD, CID360, GDPR powers that be?
- jdmichal 5y agoYou are definitely working at a different bank than I was... Mine had an entire division focused just on internal technology and tooling. Which was actually a bit of a nightmare, because it led to things like building our own cloud with customized versions of off-the-shelf software. Because of course if you ask the internal technology group whether we should build a cloud or buy a cloud, what do you think the answer will be? And of course the publicly-available version is not good enough for our super special needs, so we'll customize it and just ignore the fact that we are now either (a) on a treadmill to keep up with upstream or (b) more likely just ignoring upstream. My company chose b, until eventually years later they realized that those super-special needs weren't so special and had a huge uplift project to get to the publically-available version. Anyway, the group I worked in was an acquisition with a completely different tech stack. So we were basically completely ignored except for the occasional saber rattling that we should be moving to blessed tech stack. After which we would say, sure give us a project with time and budget reserved and we'll get right on that. Cue the crickets. Also, my group was PCI burdened, so we quickly became exempt from any of the afore-mentioned cloud stuff, because they were afraid we would make the cloud in scope for PCI. Now, most of the people who I knew were decent have left. But it wasn't about the technology -- the paycheck is enough to get through that. It's mostly around back-to-office mandates. Which is a strange stance, after the company spent who-knows-how-much moving all our machines to be virtual desktops that we could log into from anywhere.
- dialalpha 5y agoDoes your company's name start with Pi and end with co?