June 2019

243 tweets

Replying to @JanSchfr

@JanSchfr
@Lynoure @LadaNiva Der Punkt ist sicher nicht
mehr Atomkraft zu haben, sondern mehr andere Alternativen stärker zu fördern.
Atomkraft ist allerdings kein rein nationales Problem und der deutsche Ausstieg
im Alleingang verschärft aktuell nur die globalen Klimaprobleme.

Replying to @coderbyheart

They will put their life goals behind those of the company they work for, in
order to run after this tale that if immense pain is endured, massive gains are
inevitable. The mindfuck is that there is always more to do. It never ends, and
CEOs know how to exploit this perfectly.

Replying to @coderbyheart

I see it as a responsibility to point this out to younger and less experienced
colleagues whenever I notice it. Companies don't love you, so don't take their
demand for your skills as love.

Replying to @coderbyheart

Ever wonder why you rarely hear about the opposite side? Companies paying
employees more? "We workers are so grateful for the paid 4-day-weekends where we
got to go to the beaches with our 6 year olds."

If you are hesitant to sign up for
@JSCraftCamp because you don't know anybody
or are uncomfortable in unknown environments I'm happy to be your
@ConfBuddy! We can meet early and get to know
the location together and you will have somebody to turn to all time!

Replying to @HTTP_420

@HTTP_420 They are not hard to maintain, people
are too lazy to keep them up to date. If everyone makes a habit of reading and
checking the few remaining useful comments in the source code every time they
work on it they will be maintained with the code.

Replying to @fabrik42

@fabrik42 Sure, after a lot of people started
to complain on Twitter.

But they organized the conference around the idea that it is ok to charge for
food and drinks in the first place. 😡

Replying to @lukehefson

@lukehefson I'm sorry that I was not clear.

Here are my observations regarding abusing priority fields: a) Asana has a
free-text priority field, I worked in teams where we had priorities like A, AAA,
urgent, and my favorite: veryveryveryurgeng (I can try to find a screenshot).

Replying to @coderbyheart

@lukehefson This way is super confusing,
priorities need to have a clear (sortable) "rank".

b) Jira (and many others) have ranked priorities. But this gets quickly out of
hand, because new issues keep piling up and you can have an unlimited number of
issues with the same priority rank.

Replying to @coderbyheart

@lukehefson Now, if I make a list of all
issues and sort by priority, that list is totally useless in order to figure
out, which issue to focus on next, because there will be many issues that share
the same priority.

This is a broken way to rank issues.

Replying to @coderbyheart

@lukehefson That's why I want a forced ranking
of all issues, so that there is exactly 1 issue with the highest priority. If
you create a new issue and want to assign a priority the reported needs to pick
which issues are less important, and which are more important.

Replying to @coderbyheart

@lukehefson Because what sucks even more is to
have to juggle priorities between different projects (in GitHub) or components
(in Jira). You have to mentally calculate: issue priority x value of project =
actual priority.

Took the DSLR and thr 50mm fixed length for portrait shots today (which went
great), but I also love this lens for more artistic shots.

Replying to @Bahnhofsoma

@Bahnhofsoma Slack innerhalb des
Unternehmens, da ist Zugang zu PNs aber einfacher zu regeln, wie mit E-Mail wird
einfach alles als nicht-privat deklariert (über eine Vereinbarung). Dann gilt
kein Postgeheimnis für Slack-PNs und MA müssen im Problemfall Zugang gewähren.

Replying to @c089

@c089 Jira is bought by managers who want to claim
to be agile but want detailed reporting and control over resources and
information, not by developers who want to deliver value.

Replying to @KlaraMiffili

@KlaraMiffili Never give up, but always be
weary of tunnel vision, especially with deadlines. If I am stuck on something
for more than half a day, it's time to take a break, and explain the problem to
a coworker (or a 🦆) or in another way collect thoughts. That usually reveals
the next step.

Replying to @fabrik42

@fabrik42 @euruko
@Hurtigruten Have you been on a Hurtigruten?
You really can't compare it to monstrous cruise ships. They are much smaller and
don't offer any onboard entertainment (except a library and a piano). Food is
also locally sourced because they are in a harbour every day.

I was thinking the other day:

Do you use podcasts internally as a way of explaining your software /
architecture? Do you think that would be a good idea? Do you have experience
with that?

Replying to @awdng

@awdng Yes, absolutely. What I like about this idea
that in a podcast you can record an interview style conversation. This is
entirely different compared to when I only have myself to talk to, like when
writing.