The rise of functional programming in Banks
blog.oxfordknight.com
blog.oxfordknight.com
Not sure how it got picked up, but i don't think it's a creppy stalking of my profile...in fact i am flattered. Thank you for your feedback.
Couple of things that I think is worth adding here:
1. This article was the first article i ever wrote for Oxford Knight 2 years ago. The date refresh on our website is wrong. My intention was to give something back to the community I serve, and also learn from feedback. Some of it does look like I am stating the obvious, but at the time it wasn’t obvious to everyone. Furthermore, recruitment isn’t designed to be open-source. It’s all about protecting IP at the lowest level, so to open up even a little bit is a big step for us/recruiters….i hope some of you guys can appreciate that .
2. The article was written looking at how I used to recruit in 2006. Shallow, buzz word chasing, educational profile chasing etc. I like to think I’ve evolved a bit since 2006, but do understand I still have a lot to learn an certainly won’t let my non-technical background get in the way.
3. If you guys are interested in seeing some of my more recent stuff I’ve written, it maybe worth jumping on to my quora profile where I write more actively about the technology trends in london….Quora (Abdul-Muhit).
4. Finally, I do feel the pain of how recruitment operates now. Changing a £4 billion industry is not easy, and no technical innovation is going to make a sector of that size disappear anytime soon. I founded Oxford Knight with the view of creating a legacy not a transaction service business. For a boy that was raised by a single mother on benefits I have all the little things I need now! For me it’s all about creating a legacy….something built to last. Therefore, if we have upset anyone of you guys with below par service then please do feel free to email directly, and I promise I will do my upmost to fix it.
Best, Abdul co-founder of Oxford Knight
I guess it's another recruiter wondering why he gets no respect from the cattle he handles...
So it seems to be a company-wide feature. It's hard to see though how technically semi-literate technical recruiters can be a good thing at all. Perhaps this explains in part this other telling quote from the article:
I recall the candidate in question being perfect in every aspect (CompSci from top university, sound understanding of data structures, algorithms, complexity... coupled with actual practical programming experience, and oh yeah – decent knowledge of Exotic Risk and Pricing).
Note the order of qualifications, suggesting that having top marks from Oxford is just as relevant/important as knowing how to crank through data structures/algorithms questions; with having actual programming or domain/relevant experience as just a nice plus.
Very telling of their mindset, but also understandable if they are not qualified enough to assess the technical competence of candidates on technical terms alone.
I actually found this article from a non-technical recruiter informative and do respect this effort from the author. It's nice to read from a recruiter who has taken, at first glance, a deeper look at functional programming in the marketplace and shares some insights. There's some hyperbole in the article, but it seems to be coming from a honest perspective.
Otherwise it makes little sense to me too. :)
Oh, well, of course.
Interesting though this article is, forgive me for calling out Oxford Knight here. For those not in the know they are just a recruitment company. One of those that are a constant hassle on LinkedIn. It seems telling them multiple times that I am not interested in a job in finance does not stem the flow of "Forgive me, you must get this all the time, but..." connection requests and InMails, or creepy profile views.
Isn't LinkedIn suppose to be precisely for this? Also - creepy profile views? Wat.
Any ideas which banks?
One thing I've seen is a cautious adoption of Akka in distributed systems in capital markets (grid services for analysis computations being one example). First-class Scala support in Akka is encouraging those banks to take a look for specific projects.
Yeah, sure.
Guess what, there was no real crisis then either...
Abdul Muhit
There is nothing new in computing, every 10 years the same things come round again and again. That's why old geezers like me become cynics.
I do appreciate that there is an enormous list of things that are important right now, that software engineers have to worry about such as good user experience, proper abstraction, security, encryption, privacy, reusability, reliable data storage, good recovery etc etc
However to dismiss concurrency issues in a world with peaked processing powers on a single CPU as something of a fashion-fad! Doesn’t sound to me as in synch with what i've been observing.
Would be nice to hear from others on this1
B. Your last comment points to one language and the complexity of adapting it vs ignoring wider argument that there is a greater need for concurrency to add performance than what there was in the 80’s when CPU’s got faster ever year.
c. You almost indicate that despite the GIL banks are using python and therefore must be less concerned with concurrency. This is not the case because GIL in no way stops concurrent programming from happening in a single Python process. The only constraint the GIL places on multi-threaded applications is that a single Python process cannot execute multiple threads simultaneously. You can still run multiple threads.
b) computers nowadays are insanely fast - so fast that we use high level languages like Python instead of assembly. So that's not it.
c) that makes no sense. There is no point in threading without concurrency! So that's not it either.
There is no multi core crisis now, just as there was no transputer crisis back then. Only people trying to sell stuff.