March 2022

383 tweets

"Clean Code" is an opinion. "TDD" is a method.

When will people finally realized that one of those is aging, and the second is
timeless?

Replying to @feffi1

@feffi1
@w3ltraumpirat Clean Code is a set of
practices, collected based on the experience of a specific developer. There is
no proof attached, only anecdotes. This makes it an opinion, which is taken as
"rule" and proliferates as "wisdom", but it's value is mostly inflated through
marketing.

I've reached 4,000 followers on Twitter, and I am grateful to have this site
every day. It's a way to stay in touch with friends, and find people that share
similar interests. It's also an important tool for professional exchange. Great
to see so many of you share my interests!
Embedded Photo

Replying to @coderbyheart

I always recommend Twitter to young developers, because it's an awesome way to
learn from others by following them. It's a bit random, but you get access to a
lot of gems and can easily cut through the gatekeeping pay-for-education system
that's still very common in our industry.

Replying to @coderbyheart

My tip to find great people to follow in tech is to start with conferences you
can't attend; look up their speakers list and follow them on Twitter. From their
profiles look who they are following. Grow from there, and don't worry to
unfollow / mute someone later!

Please be mindful with disclosing personal information when adding yourself to
lists like this. Keep in mind that there are individual and groups who will try
to disrupt support efforts like these using violent measures.
/status/1499448090817875969

Really nice improvement by @GitHub pages: it now shows the status of the
provisioning of a custom domain for GitHub pages.
Embedded Photo

Watched "The Batman" today. Pretty dense story but they got 3 hours to fill, and
great performance by Pattinson, both physically and emotionally. Some truly
iconic cinematics and monster sound!

Replying to @_vojam

@_vojam It's equally possible. Embedded source
code is not different than other source code. But it depends on your model for
pulling in upstream changes. For example the Nordic SDK is a fork of Zephyr and
following their releases requires use of a branch, which lasts for a long time.
>

Replying to @_vojam

@_vojam That's not the main point of TBD,
arguably you can always deploy branches as well. The point is to get rid of
merge hell and foster a culture of knowledge sharing, because everyone needs to
be aware of what is happening in the codebase.

Replying to @_vojam

@_vojam Still not sure what you are trying to
achive. But you can start the transition for PRs to TBD by reducing PR size, and
for smaller modifications use ensemble programming (work on it with a colleague
together) and push it directly to trunk, it's automatically reviewed then.

Replying to @alex_schl

@alex_schl Do it, if you get the chance. It's
that much actually, roughly a third of the book is spent on explaining the
methodology. So you can get the main parts done in a day. I think it would be a
good addition to your great selection!

Replying to @krikkert

@krikkert
@pati_gallardo What I find most problematic
is that the frame it on behaviour around attendees of the event. That's sounds
like a bit of a cop out, because they don't have to care too much about what a
person did until they actually attended the event.

I mean @awscloud lambda is awesome, but it still
blows my mind that after 7 years they still haven't managed to ship their own
SDK releases as part of their Node.js runtime.

Had a discussion today about denying access to a digital service based on users
location. What a time to be alive. :/

I don't think it's good to restrict access to global infrastructure. Everyone
needs more, fairer access, not the other way around.

Replying to @Ravetracer

@Ravetracer Ja, da oben gibt es Messtationen,
die besonders auf "Funkstille" angewiesen sind (is ja sehr weit entfernt von
größeren Siedlungen). Daher sollen dort jegliche Funkwellen vermieden werden.

There is no change without pissing some people off. But is it worth keeping the
status quo, for a few calcified die-hards who benefit most from no change at
all? #diversity

Replying to @fquednau

I am looking at hundreds of CVs from students these days, and what baffled me
the most is the complete absense of IT related part-time jobs in there. Students
work in stores, restaurants, as instructors. But noone works in a company that
does some form of software development. 🧵

Replying to @coderbyheart

I talked to our students (which now obviously have a job in software), but they
confirmed this for #Norway: there is little opportunity for student IT jobs,
simply because of the abundance of people with finished education. This allows
companies to be picky for entry levels,

Replying to @coderbyheart

and they do not have to rely on students to fill the gaps. This is so different
to my time as a student, when many of us had good paying jobs working in small
IT shops, marketing agencies etc. It's such a missed opportunity for many
students to learn more about the field they

Replying to @atyborska93

@atyborska93 Same pattern here. It seems
pushing more people into higher education is causing this. Companies are
optimizing for their ROI and rather wait for a better trained candidate they
haven't invested in than start early building a relationship.

Replying to @Twittfort

@Twittfort We like to be prepared, because we
know things will change. And then we prepare for what we think will come. And
then something else happens, but the thing we prepared for initially could still
come. So we pile on.

Replying to @ShivamJoker

@ShivamJoker Cold start time will likely be
slightly better with bundled code (all needed code is read from one file). It
won't affect regular execution performance. But in practice, using a layer will
not have a significant performance impact.

If you chose to be non-political as an organization in the question of the
Russian war against Ukraine, you are being policital.

Replying to @coderbyheart

"We need to discover the right problem, before we start to discover the right
solution. Problem discovery must be a function of the team, not outsourced to a
product manager."

Replying to @coderbyheart

The point is making is that we need diverse teams with strong communication
skills to build great problems. Because evolution favours the best ideas, but in
teams we often artificially limit our inputs.

Replying to @coderbyheart

"Hire students to test your onboarding process, and they make for great guinea
pigs, so you get a chance to also try run working with people. If that's not
your thing, there is a natural way out, they just leave after a while
automatically."

Replying to @Niklas_L

@Niklas_L
@chaugstvedt Yes, but this would only ensure
visual aspects of your app, and I think you would spend a lot of time defining
good sample data. It's also not strictly a unit test if you have to ensure
rendering of two components does not break the UI.

Replying to @coderbyheart

@Niklas_L
@chaugstvedt So, Im trying to find a
screenshot, but I have recently used a mobile app, with a textarea and a submit
button below that. Once you click into the textarea, the Android keyboard
overlaps the submit button, and you weren't able to hide the keyboard without
navigating away.

In tech we need to stop being (busy/fully utilized) all the time so we (have
enough time/are bored enough) to (try out/invent) new things.

Replying to @coderbyheart

I have worked e.g. with organizations like
@Code_Door, where we got asylum seekers the
skills needed to find a job in tech here in Germany. This is one example not
aimed to put pressure on wages, but totally realize this is a good motive why to
run a code school.

Replying to @coderbyheart

And scams like Lambda School also jump in and prey on inexperience people who
buy into the omnipresent urge to need to learn to code. It's pretty wild west
and hard to find a reliable, trustworthy program among all these opportunities
for scammers.

Replying to @byteborg

@byteborg Ist halt extrem teuer durch kleine
Importläden zu gehen, die Produkte zu entsorgen und den Produzenten im Ausland
zu verklagen. Zudem musst Du erstmal den Markenrechtsstreit gewinnen.

Calendar: is impossible to deal with in precise ways.

Humans: argh, there must be something better.

Swatch: I give you .beats!

Humans: No, that would be too easy!

I believe files are the worst option to organise source code but we are too
locked into this concept from the 60s on so many layers that it seems impossible
to break out of it.

Replying to @borderless_dev

@borderless_dev I imaging code layed out
on an infinite three-dimensional canvas which is self arranging according to the
flow of data, and you can easily jump between code segments that are connected,
and also have a instant way of filtering / teleporting anywhere with a few
keystrokes.

No education can prepare you for the right choice of the 200+ AWS services for
your project, only building solutions can.

Replying to @_StephanRoth

@_StephanRoth But for sure, if it's
triggered you are likely killed by shrapnel. However these are
pressure-triggered (by heavy vehicle), because they are usually buried. But they
are OK to be handle by hand (if in undamaged condition).