- Open – to consider for yourself
- Interesting technical problem you solved lately
- Interesting technical problem you solved during your career
- What is the process of the MR/PR change review for you
- What is great success you accomplished lately? What skill did you improved lately?
- What is your greatest failure during your career? What was your biggest mistake?
- software design approach
- software should be driven by business domain
- pieces of software should match the business domain
- domain is primary focus
- complex design should base on model of the domain
- devs and business should continuously work on refining this model to address changes in business
- common language for defining a business model of the domain
- complex logic should be abstracted to domain
- based on TDD
- better collaboration between devs, QAs and business than TDD
- behavioral tests first, implementation second
- behavioral tests should be easy to understand, simple
- those tests should be written in specific language, possible to understood by business
- combines idea of unit tests naming, acceptance tests standard agile framework (As a XXX I want YY to achieve ZZ), and acceptance criteria with Gherkin
- software requirements are converted to tests cases *before* actual implementation
- implementation is done against all those test cases
- opposing to first writing an implementation then tests cases
- software often waits for some I/O operation to complete (file operation, network call, database query etc.)
- we can use this time for something productive instead to wait for data to be available or I/O operation to be completed
- with asynchronous programming user can work in the meantime
- not waiting for I/O operations synchronously enhances user experience
Of course this problem is much more complex. Modern software operates on much more different PC architecture than 20 years ago. Nowadays software must be asynchronous to appear more user friendly and to made better use of modern multi CPU architecture. Right now complex, professional software uses multiple processes, threads on multiple CPUs (CPU you buy is not really *single* CPU) or even utilize GPU for more complex computations (like i.e. video editing software). Before that we mostly had single threaded desktop applications that had ‘please wait’ or ‘loading’ pop ups. Right now this is song of the past really and to achieve better User Interfaces that allow to edit tag of your post without changing whole post. With mobile devices on the rise and sometimes lousy cellular network those kind of designs would not be sensible or sometimes impossible to implement. Did you ever happened to reenter some chunk of data into some software because you lost it? Maybe network was down? Or you hit back button by mistake? Right now it belongs to past mostly. All of those would be hard to do with synchronous operations. Right now people are bit spoiled and they tend to leave the page/application if it appears to be slow and not every company can sell ‘one-in-the-market-necessary-for-your-work-software’ that you will be forced to use. And this is why we have asynchronous operations and this is why we have asynchronous programming model that allows us to program such operations.
From the technical point of view we hit bottleneck with faster CPUs every new generation. CPUs started to be very hot and power hungry about 20-15 years ago. That kind of progress was no longer possible CPU manufacturers started to implement Hyper Threading and squeeze more cores into single chip. Still software were mostly single threaded but when home use CPUs started to gain traction (mostly because were cheaper) software needed to caught up. I remember working on mostly single threaded desktop application around 2011-12. Company was trying to use of multi threading to modernize it via Thread Pool usage. Eventually hardware and framework and libraries caught up on this new trend. With those possibilities and new tools it was finally possible to write software that use more than just one single CPU core. After mobile phones started to be popular it was even more important since their architecture and low power makes single, fast frequency CPUs impossible. It becomes necessity to write software with multi threading in mind. Eventually with web application gaining traction and browsers becomes sandboxes for those it was possible to write complex JS applications with asynchronous, multi threading operations.
With all of those possibilities and changed environment it was the only choice for IT world to make asynchronous application standard. And with this new standard way of coding changed and applications design changed, so now you can open your messaging app on your phone and and add photo to the message and send it at the same time. And then close it – while upload is still being done. If this fail you will be notified. If this will succeed – it was success due to asynchronous programming.