May 2019

224 tweets

The best designs in software emerge from building working solutions and step by
step widening the scope, not from sitting around a table and writing
architecture specifications.

Replying to @coderbyheart

Especially the constant switch between Slack and GitHub is annoying, so having
all code-related discussions on one platform is great.

I wish @github teams would offer integrations like
Slack does, for getting real-time notifications in (logs, metrics, errors).

@franzen_simon I think they are laying a
barrier in front of the brown wooden house on the ground of the river. The house
is very old and slanted and I think they want to build a support structure to
keep it from collapsing eventually.

Replying to @coderbyheart

@rinkkasatiainen
@SoCraTes_Conf I think in general thinking
about user needs is super important and should always come first. I should drive
the next changes.

I see however that there needs to be work put into discovering user needs. Most
of the time they are not know, because users rarely take time to share.

Friendly reminder that there are different testing strategies because none of
them will catch all kinds of bugs.

Make sure you cover all segments of the test pyramid!
Embedded Photo

You can tell great consultancies by the amount of time they invest in their
people to undo all the stupid things they learn when working on client projects.

Still amazed about this great application using our #nrf91:
https://anicare.fi/en/

The device is attached to animal’s earflap and it autonomously measures
different vital functions of the animal for a time span of approximately 👉 two
years 👈.
Embedded Photo

Let's say I know about a serious leak of PII at a bigger US-based company and
already have reached out to their support, but they did not react. Who would you
contact next?

Do you also have this not yet so old couple among your relatives that is quite
good a digital communication but you never know who you are talking to because
they share every account?!

Replying to @zjklnwp

@chgpxyi I love JavaScript, but Python is a much more general purpose language
and arguably used in a more broader context. It is very beginner-friendly and
there are great resources to get started. In addition switching from Python to
JavaScript is not too hard later.

If you just started to newly talk to and Event Sourcing/CQRS backend one aspect
might not be obvious for you: optimistic updates are your friend!

From synchronous REST APIs we are used to this: write, read, update. >

Replying to @coderbyheart

You write (POST) to change the state of the system and then read the new state
of the system (or get it back right away from the POST), then update the UI
state with what you received from the server. However with ES/CQRS systems you
normally will be done with the write part.

Replying to @coderbyheart

The result of that is an event and if the write is accepted you should
optimistically update your state of the system right away and go on about your
business. This will drastically improve the responsiveness of your UI and save
you a lot of round-trips.

The cool thing about hiring #junior developers is: regardless of their
experiences you can train them for your needs AND you will learn more about your
own tech by doing so.

Replying to @TonyBologni

@TonyBologni SAFe is loved by traditional
organizations because everybody gets to keep their job, including the middle
level manager whose sole existence stems from controlling the flow of
information (some call it Lehmschicht, Permafrost [T-Mobile], in Germany).

Replying to @TonyBologni

@TonyBologni Because they are a product of
their old organizations and never learned to be that. It takes time, training
and individual coaching to unlearn toxic behaviour.

Thinking that they "just" can be different is exactly what many transformations
do and that's why they fail.