Wolfram Rittmeyer

Google Developer Expert for Android and the Google Assistant.

Blogging on Grokking Android (

[Wolfram Rittmeyer @RittmeyerW]

Very proud to be on the advisory board of next year's Kotlin conference by the German Publisher Rheinwerk. @rheinwerkverlag @kkonrheinwerk

https://t.co/xTVErTE7NA

#Kotlin

[Android Developers @AndroidDev]

Get the details here! ↓
https://t.co/DTmmWb2xKy

[Niklas Lochschmidt @Niklas_L]

The most useful information I can often get about a certain piece of technology is about its downsides and trade-offs.

I started to write about what I would have personally liked to know about #Kotlin 3-4 years ago.

https://t.co/SYGS65MfXp

[Márton Braun (write-only account) @zsmb13]

Check out our new coroutine testing guide, hot off the press! 🧵🧪

https://t.co/F45O266G03

In this guide, you'll learn how to use the testing APIs new in kotlinx.coroutines.test 1.6, as well as the best practices you'll need to test your Android code!

[Wolfram Rittmeyer @RittmeyerW]

The CfP for the next edition of Rheinwerk's KKon is open. You can either submit your proposals in English or German.
https://t.co/0cD3OnKDts

#Kotlin #Android

[Wolfram Rittmeyer @RittmeyerW]

@justabadrobot Really, really sorry, to hear this. My heart goes out to you!

[Android Developers @AndroidDev]

🔍 Join us on October 27-28 for #AndroidDevSummit 2021!

The code is solved and we can't wait to see you there.

Save the date → https://t.co/MIld7Bt1Jb

[Wolfram Rittmeyer @RittmeyerW]

@ParkinJim @exitthelemming @subsymbolics I don't. But good question. If you find out anything, please let me know.

[Wolfram Rittmeyer @RittmeyerW]

@exitthelemming @subsymbolics They disqualified her, yes. Unbelievable nowadays, but sadly true. But nevertheless it was only one who actually tried to stop her run.

[Wolfram Rittmeyer @RittmeyerW]

@mreichelt Yep. I'm using it for a Bitbucket pipeline. Everything worked fine. Thanks!

[Wolfram Rittmeyer @RittmeyerW]

@mreichelt I'm normally using the one that fits the target-sdk (still mostly 30 for now). For one project with targetSDK 30 I've just switched to your new android:31

[Wolfram Rittmeyer @RittmeyerW]

@ASalvadorini @PreusslerBerlin But all in all I would try to expose methods that are more meaningful and directly return proper objects like toAccount(), to Customer() or whatever.
Depends on what we are talking about :-) It's obviously different for a library doing the parsing versus code using such a lib.

[Wolfram Rittmeyer @RittmeyerW]

One more on the naming front (different library btw):
public HashMap<String,UsbDevice> getDeviceList() {}

Java is not the worst part here :-)
Why can't they name it getDeviceMap()? And why not simply return a Map?

[Wolfram Rittmeyer @RittmeyerW]

@ASalvadorini @PreusslerBerlin Isn't it decodeJson()? I think this name is pretty good and better than toMap(), which is totally meaningless or toJson() which sounds like you turn something _into_ Json.

[Wolfram Rittmeyer @RittmeyerW]

@PreusslerBerlin Actually about a year ago I started something about libraries that I never managed to make useful. Maybe I should try again.

[Wolfram Rittmeyer @RittmeyerW]

@ASalvadorini @PreusslerBerlin In this case it's not an implementation detail but part of the API (the return type).

But that it's a _HashMap_ should be an implementation detail and not be part of the API. Adding Map to the name is still a bad idea and not descriptive enough.

[Wolfram Rittmeyer @RittmeyerW]

@karandhillon95 As if this were an open source library. I'm not that lucky.

[Wolfram Rittmeyer @RittmeyerW]

@PreusslerBerlin A better solution (keeping Java for now) would have been a method

UsbDevice findDeviceByName(DeviceName someName)

plus a simple

List<UsbDevice> getDevices()

that returns all devices, if you want to iterate over them for whatever reason.

3/3

[Wolfram Rittmeyer @RittmeyerW]

@PreusslerBerlin Because you do not get devices only, it would be helpful to know what is mapped to what. That's why getDevices() feels odd to me.

But, I guess, the method in itself is shite - and that's the root cause for why getDevices() in this case feels wrong.

2/x

[Pauline Schmidt @pln_schmidt]

Die wichtigste Karte, die ihr zu #COVID19 kennen müsst.

Indien und Südafrika haben bei der Welthandelsorganisation eine Anfrage zur Aussetzung der Patente/Medizin gegen das Virus gestellt. 100 Länder stimmten zu.

Die roten Kreuzchen sind die blockenden Vetos.

Hello Europa!?

[Wolfram Rittmeyer @RittmeyerW]

Naming is hard. One constant of a lib I'm currently using is "ERROR_SUCCESS". Now is this an error or is this a success?
As a quick rule of thumb: If devs need to look at your JavaDoc/KDoc your naming is wrong!