| ▲ | lxgr 4 hours ago | |||||||
"Not thinking, just complying" isn't the panacea for good outcomes you make it out to be. You definitely want to limit the amount of excitement, but I've seen many issues caused by legacy formats and practices as well. > You comply with your employer's practices end of story. What if you're the employer ("first engineer" etc.), and there are no practices yet? Fintech almost by definition sometimes includes doing things from scratch because some existing solution or incumbent organization isn't working that well anymore. > Unless its your job to architect stuff Which seems to be the target audience/scenario for TFA. | ||||||||
| ▲ | traceroute66 4 hours ago | parent [-] | |||||||
> What if you're the employer ("first engineer" etc.), and there are no practices yet? In that scenario the practices will still come first. You're not going to be doing any coding or systems engineering until you've got compliance signed off. You're going to be spending lots of time with lawyers and compliance people. > Fintech almost by definition sometimes includes doing things from scratch Yes, but cut through the noise of the typical Fintech fancy website and app and you're still staring straight down the barrel of spending 80% of your time on regulatory compliance. Try as you might there are only so many ways you can re-invent the wheel for dealing with hard-facts legislation. | ||||||||
| ||||||||