Nik Slezkinsky, Head of UX Design Department at Devexperts, shared his vision on building award-winning trade application UI’s
Interviewer: Can you describe the Devexperts Design Team working process?
Nik: There are two ways to develop a UI. The first one is when we are free to create a product from scratch. Starting from scratch is easy, as we have full control over the implementation process and the result. In the second case, clients provide us with logos, colors, and maybe some more guidelines, so front-end terminals design is built under certain constraints. Here the story is unpredictable every time as we may have some challenges to overcome. For example, a client might want Read more…
Enjoy a challenge? Our mission in early Spring 2016 was to develop a live prototype of the OTC flex-options trading application in a very short space of time. Join the Devexperts Mobile Development team on a journey of discovery as we set to work at finding the ultimate solution.
In a not so distant past it used to be the norm to essentially perform all trading operations manually – with a phone in one hand and a spreadsheet with your positions in the other. The teams’ overall goal was to automate current workflow allowing traders to monitor their options portfolio on the fly and simultaneously analyse risks.
Phase one of this exciting project involved developing a desktop application and a mobile solution – iPad app. Working closely with designers and the UI/UX team to implement as much functionality as possible, the overall achievement of delivering this comprehensive product on time was impressive. The project started in early April and had to be completed by the designated date in late May – and not a single day later. In total, the team had only had 6-8 weeks pure development time. Read more…
Software companies increasingly have a variety of different projects to manage. Sometimes these projects are similar to one another, or at least they have some common functionality, sometimes however they are not. Overall, the majority of projects business analysts and development teams work on contain very similar (if not the same) portions of functionality, defined in the project scope.
Let’s not forget about high rotation of people, not only between different projects, but also between different companies. Not everyone involved will necessarily have a deep knowledge or understanding of the product functionality or even the business area the project is related to. For new-coming analysts, the problem of understanding the business area could be easily resolved by Read more…
Colleagues and friends,
Our close-knit company has suffered a tragic loss. On Saturday, our friend and colleague Artem Kozyrev, a warm-hearted and inspiring person, fell through the ice to his death.
Artem was one of the co-founders of the company, the person behind the first versions of the TOS and Thinkpipes platforms and a great source of expertise on option trading. Artem was a kind, wise and open-minded person with a positive attitude. It was great pleasure to work with him because of his exceptional friendliness, outstanding intellect and knowledge. He was always determined to do the right thing the right way.
Artem was a loving husband and father of two young children.
Usually, it is good practice to automate any kind of routine. In testing, automation is vital. It helps decrease costs, makes testing tasks faster, and improves efficiency of your staff. It is a “no-brainer” to think about automating different testing tasks, especially when reading marketing materials or listening to a sales presentation of a “leading- edge-premier” robot software. Those reports are usually based on success stories from the world of the most complicated user interfaces – CAD software, graphics software or maybe some examples of extremely complex but good web design. Moreover, usually, these reports are true. But you should think carefully before starting a GUI test automation project. In many areas of software development, GUI automation is not so easy and obvious, and your entire automation project can quickly turn into disaster, in spite of the visual attractiveness of the tools.
Devexperts is a global company. Our offices are in different countries and cities, our company is made up of different projects and technology teams. That’s why we seek to support our internal unity and common values throughout the company.
The company’s internal blog is the main media where project teams share their work experience and ideas. The post you are about to read is taken from Devexperts internal blog, but we are sure it will be equally interesting to our friends and clients . The post is devoted to the release of our trade applications product suite, called “dx”. There are currently seven of them . They are based on different platforms: web, desktop, mobile and specially designed for different form-factors and OS.
Have a nice reading!
My name is Nick and for those who are not aware, I’m leading the team responsible for the “dx” user interfaces and user experience. We design both Devexperts own “dx” applications, and white-labeled applications based on “dx-technology”.
Weinberg’s Second Law says that if builders built buildings the way programmers wrote programs, the first woodpecker that came along would destroy the civilization. In practice it means that any software has to be tested very carefully to fix bugs in it in the earliest stage of its lifecycle.
Rapid expansion of multicore and multiprocessor systems makes software developers write parallel programs to use system resources as efficiently as possible. And here another big hazard is hidden – errors, related to incorrect usage of multiple threads of execution. On big production servers it’s a much bigger threat than it seems, because the program code is physically executed on different cores or processors, and concurrent issues arise in their full capacity. Most well-known problems of such a kind are deadlocks and data races. All concurrent issues are hard to detect manually or by testing, because their nature is essentially nondeterministic. Data race detection is an especial issue, because the effect of their occurrence may become apparent much later. When a data race occurs, global data are corrupted, but the application itself doesn’t halt, it continues to work with incorrect data, and who knows when one would notice it. Data races may be really dangerous – e.g. data race was the cause of accidents with Therac-25, the radiation therapy machine, that gave massive overdoses of radiation to six patients. Also data race was one of the causes that led to the Northeast blackout of 2003 that affected more than 50 million people in the US and Canada.
Good news Read more…
Roman Elizarov – Devexperts Board member and Projects Coordinator, Director of ACM ICPC contest finals 2013 shares his experiences of the ACM ICPC contest finals organisation. ACM International Collegiate Programming Contest (ACM-ICPC) is an annual multi-tiered competitive programming competition among the universities of the world. The contest fosters creativity, teamwork, and innovation in building new software programs, and enables students to test their ability to perform under pressure. Quite simply, it is the oldest, largest, and most prestigious programming contest in the world. Roman is not the only person in Devexperts, who is concerned with ACM ICPC, but the most known one.
I would like to start this interview with congratulations. Participants and guests appreciation of ICPC finals contest organisation is very high. Do you feel that your efforts have been rewarded by everybody’s recognition?
Yes, it was an extremely rewarding experience. It turned out much more rewarding than I had anticipated. Read more…
“Millions quotes per second in pure Java”
Writing software that works under high load is an art that requires a lot of skill, regardless of the programming technology that is being used. Java platform is an ideal choice to create big and complex software systems because Java is the most popular programming language, has the largest talent pool, and its features, tools, libraries, and community around it provides for the highest development productivity. There is a great deal of the criticism about Java performance that you can find on the web. But, as numerous academy research had shown, the performance of the software code strongly depends on the skills of the authors who had implemented the code and much less so depends on the technology that was used for its implementation. Of course, each technology has its strong and weak points. For example Read more…
I’d like to dedicate this post to Mark Zuckerberg, even though I fully realize he doesn’t care at all. But still his famous quote with regard to HTML5 being very impactful started many discussions and changed the way how a lot of people saw the mobile technology landscape at that moment.
He’s usually quoted like this:
“When I’m introspective about the last few years I think the biggest mistake that we made, as a company, is betting too much on HTML5 as opposed to native… because it just wasn’t there.”