I haven't read the book, but I've followed the chatter and have been listening to Lewis on Bloomberg. I get the impression that many justify HFT by comparing current or past alternatives, however his argument is that HFT is corrupting an otherwise fairer market place. In other words the market should improve and lessen these side businesses that victimize participants and add to the discredit of the exchanges.
If anyone thinks that these side business do not victimize participants you should look back to examples like Knight Capitals glitch that most certainly caused retail investors to lose trust and pull their money from the market, taking a loss. The introduction of non-relevant code is an unnecessary risk that does corrupt the system and does victimize your average investor.
It's sad that I as a retail investor need to spend my valuable time focusing on how not to get screwed by the exchanges that have introduced a side business which does not serve the functioning of the market and instead corrupts it.
This may appear spammy, but I found Kepner Trego training[1] to really help prevent this kind of stuff from happening. The strategy is more effective when everybody in the room has had the training, which limits its usefulness with external clients, but I'll still recommend it anyway.
So you think BA's can not learn, even through experience, what can or can not be done?
Sure, there's always somebody else, same role or not, who has more expertise, but don't confuse role/title for expertise. I've seen BA's with a decade of experience school junior engineers on what can or can not be done.
> However, this is illustrating a particular problem that only affects engineers -- engineers are the ones at the end of the day who have to make a solution reality.
This is simply not true. In the past I was a Business Analyst. I would meet with clients to gather requirements and that illustration would often unfold in the same manner.
It has nothing to do with a persons role, it has everything to do with having large knowledge or expertise gaps.
I'll suggest there's a missing ingredient here...I found I was able to eliminate many of my comments by asking myself if that someone whom might read my code would be better served with a unit test instead. I also found, however, that this needs to lead to an understanding that unit test are in fact a form of documentation and should be treated as such.
yeah, i should have said in high quantities, but I was just paraphrasing the video. The point was, in the video, he did not say it was just fructose, glucose can also be a problem.
I'm pretty sure, in that video, the argument was that while glucose is still really bad for you, fructose[1] is much, much worse - it's a poison that's causing an epidemic.
1. And specifically the manufactured fructose isolates vs. natural fructose found in fruit.
Edit: rather glucose in high quantities as noted in response below.
Ever seen those web adverts that list a few generic health problems and ask you to 'click here', or read a horoscope that makes claims almost anyone can relate to?
So how is this different? Why so many upvotes...really, this is just more spam - is it not?
I wouldn't discuss with the Microsoft rep. This is a decision your school needs to make.
You could politely decline to participate and provide your reasons for doing so. If your department feels strongly enough about it then let one of them volunteer to do it. If no one volunteers, then obviously they don't feel strongly about it. Your declining to participate sends a strong message.
Unfortunately, things like this are more damaging overall. i.e. Even if you succeed and get some more women involved, you will have also created resentment from men whom are not given equal opportunity, which then can lead to women not being given equal opportunity.
I suggest you don't perpetuate the problem / don't participate.
I downloaded a rss reader app then put in the main HN link, but the app rejected it. The RSS link worked. This may seem obvious to some, but may help others.
When I make mistakes, which I often do, I don't go around thinking oh, darn, they should have known that for me. That goes for using a bad framework or lack thereof.
As I said, I'm all for having a great framework, but I would not excuse the mistakes being made here, and I'm simply saying that I believe that my products and my knowledge level benefited by not having one.
> Having bad password management and opening everyone up to CSRF and XSS is not "trivial".
I'm not suggesting everyone should need to be aware of these issues, I'm saying someone on your team should be. And if you're a team of one, be prepared to make mistakes (which will not be limited to the issues outlined here).
> The argument here is "build a clojure framework lots of people use.
The argument I am addressing is that people are deploying products with poor security because a great, all encompassing, framework does not exist. There's no excuse for doing that.
This is not about having to understand cryptography, it's about knowing when and where you need to use it and making sure it's included when you do. The issues outlined in the video are trivial.
vs. a what? I've worn many hats in my day, the least of which has been a developer hat.
There's equal risk in relying on a code base incorporating features with underlying concepts that you or your team does not understand.
I'm all for having a framework, where you can review the code and be comfortable with what you're relying on, but in the absence of having a good one, well then build one. The benefits Clojure brings to the table more than make up for the work in either case.
There's just no excuse for not knowing the concepts and not knowing if your product needs them.
If anyone thinks that these side business do not victimize participants you should look back to examples like Knight Capitals glitch that most certainly caused retail investors to lose trust and pull their money from the market, taking a loss. The introduction of non-relevant code is an unnecessary risk that does corrupt the system and does victimize your average investor.
1. http://www.telegraph.co.uk/finance/newsbysector/banksandfina...