Deploying on friday is absolutely fine, as long as it fine to fix the problem on monday.

But that happening is quite unlikely

And than you realize the used framework only exists for 3 years...

Answers from 2005 might or might not be the answer youre looking for...

Just set a timer, once the time is up you go back to work. This way people get the hang of it pretty fast.

@Elyz well one scenario could be a intern is asked to create a poc.
The intern decides that a password in plain text would suffice for the time being.
A manager only sees the front-end and is very impressed by it. He wants it put in production asap.

Intern not having a clue about the password anymore just does his work and leaves the company.

End result: an web application which has passwords in plain text

But what if, you put that docker also inside a docker?

There are also regular USB where putting it in either way works. I believe JBL have those for the new usb power adapters

@Hastouki well its quite innocent. Every now and then a colleague asks for help by skype. So i gladly help by sending an piece of code as example via skype. But once he copies it in the IDE it cant compile...

So the knowledge is not the dangerous part it are the people who misuse this feature that are ;)

Copy code into skype, copy code from skype back into codebase, sit back and enjoy.

Fyi: i dont know how/why but if you copy something in skype it messes up the whitespaces and stuff.

Start with @D--M as a baseline. Most important part is always just doing and dont be afraid misjudging stories because exactly those stories will add value to the points you give later.

Scrum is about being transparent and always try to inspect what you do and adapt to it to improve. So JUST DO IT!

Well I can answer this “issue” for you as a backend dev.

The longer you need to compile, the more coffee you can get

I wonder how many of the visitors/customers are actually programmers?

You forgot to add a TODO: to it.

That moment that your application reaches the amount of 1000 tests and still all pass.

Well it was auto-generated when i got my first docker container running.

@LabMember003 Oh linux is no problem, I really like elementary OS but sadly for my work we dont have much choice.... but thanks for the tips!

The most frustating part is you really want to write tests for it but sustaining them is sometimes more work than writing the code.

Get in ear headphones and play the most annoying song you know but turn the volume so high others can hear it.

Give kotlin a try!

Versioning of your api is always nice, especially when the backend API is public to multiple applications.

Other way of doing it is to initially add stuff and only remove when the frontend changed their code to only use the new stuff. This way you’re always backwards compatible. Things could get ugly tho if you add too much.