Bumerang

In agile (from my perspective) you rely on constant feedback from the stakeholders (customers, Product Onwer, sponsors) and iterate on it - that's why it's crucial to have short sprints so you can contain the uncertainty and make sure you're heading in the right direction.

In the 'iterative waterfall' you usually split the work into several domains, with each iteration taking months up to a year. E.g. when implementing new core banking system, the first release could be 'move the customer masterhip into the new system'.

Sorry for misunderstanding, I meant that business processes are usually derived from the regulatory requirements, not IT processes. The following implementation is then affected by those regulations - again, in a way that limits potential differences between the desired outcome and implementation choices.

You don't do the whole implementation at once - you usually split it into several chunks/releases and everything becomes more manageable. I am a fan of agile where it makes sense - in projects/products where you have a strong uncertainty about the actual outcome/desired product. Then agile gets you there faster and cheaper.

But what people seem to forget about is that waterfall is actually cheaper in those cases where you have a clear understanding of the needs, the end product, and actions and tasks you need to do. This is usually the case in banking - you usually have a box product you need to customize and integrate (the toughest part, and processes are pretty much set (also strongly determined by the regulatory requirements). Hence, most innovations are just automation of specific process steps.

Another thing to consider is that the people in the bank are used to work in this way, so it removes some traction and gets you up to speed faster.

Yeah, currently working on a project implementing new core banking system via waterfall. You can still see it quite a lot in these extremely risk-averse industries (pharma, finance, insurance).

Speaking from experience -- GDPR is a huge issue basically for everyone in the Financial sector (banks, insurance, etc.) and projects to address that started two years or one year ago. Now they are usually rolling their solution into production.

Our company is doing several GDPR consulting projects, with final delivery date around March. The interest from the companies on GDPR consulting has really decreased in the past months.

As an individual, you may consider a DPO (Data Protection Officer) role for several companies -- these are usually too small to have a dedicated person, but they need it according to GDPR. No formal education or certificates required, however you do need to know the law and technical things on a reasonable level.

Having exactly the same background (system programming, linux, c/c++, python, never touched Javascript nor web development) I did the very same recently.

My solution was to use Django (DRF) for REST API and React for the front-end and Zurb Foundation as UI framework. Javascript is really easy to pick up and there are plenty of tools and tutorials available out there. Used Facebook JS SDK for FB login and sharing (because it's easy and ready to go, plus FB is popular enough to make the effort worth). I also used JWT for auth and session management, just to explore it and because it seemed simple enough for my purposes. Django will solve most of the security concerns for you.

In total, took me ~4 months while working full time to wrap my head around everything and build the website + deployment (Nginx, Fabric, Celery, supervisor... all the usual stuff).

I choose several words describing the project and look them up in a Latin dictionary. These are already a natural sounding words, so you may tweak them a little.

Pros: the domains are almost always available, sounds classy and trustworthy

Cons: it usually doesn't describe what you do just by the name of it.

Not sure if exactly technical, more like a meta-skill.

Learn how to analyse and decompose problems. There always will be some.

For me, the biggest problem is the start of the (boring) activity. Once I'm already in it, I can work for hours -- just the first step.

So my solution is simple. I say to myself: "I'm not gonna work on that boring thing, I'll just have a look at it." This relieves the pressure and allows me to get started. Next thing is: "Ok, so I'll just do this one little thing." Three hours later: "Shit, it's done.".

Also it helped me to write down activities I want to stop, e.g. "No HN before 5pm; No news before 5pm".

And the last thing is to remove all possible distractions. Put your phone out of your visual field, block sites, etc.