hello, Kai!

Hello Mark

how can I help you today?

Have you read "Clean Code" by any chance? Or similar books?

not in a couple of decades

So I guess you can't recommend any?

no, sorry

How did you come to your way of structuring code?

if you are referring to book examples, mostly those tend to follow the general patterns set forth by Google and other Android experts, that I have learned from documentation, blog posts, presentations, etc.

I was more wondering about your personal style

and where there are multiple choices, I tend to pick ones that I think will be popular longer and/or are ones that I think that I can explain better

I guess I'm not certain what is covered by that, sorry

can you give me some examples?

Hm

It's hard :)

I have no specific example right now.

¯\_(ツ)_/¯

The reason for that question is that I started reading "Clean Code" and didn't understand one of the examples for good code. And after some time I decided that that example maybe isn't as good as the author thinks.

And that I might have to find different books with additional ideas

To eventually find my own "style" of programming, how to structure code, how to make it readable and maintainable and so on.

well, for that, it's a bit like riding a bicycle: you learn by lots of early failures

eventually, you will learn what sorts of patterns and structures do and do not work well for the way that you tend to think about programming

blending those tendencies in with those of others -- whether they are teammates or experts -- gives you practical approaches that you will feel work and work well with others

as you migrate to new environments (say, switching from Android to iOS), you start over, though with more experience to more rapidly get to a good spot

I guess that there is often an underlying "theme" to ones programming.

Which you try to take over when you learn a new environment.

Like "I like readable variable names" :D

right, and some elements will carry over nicely, and others less so

Instead of "prioFct" or idEl

I sincerely hope those were random key sequences and not real variable names that you have encountered :-)

The second one was

The first I encountered, the second one I invented.

prioFct is especially nice as it describes a feature that neither the original programmer nor the team that probably requested it remembers about. So it exists but no one knows why really.

(As there is neither a specification nor explaining comments or anything of the sorts).

yeah, I would not recommend that as a variable name, and that's where code reviews can help, to try to prevent that sort of thing from getting into the code base in the first place

I think I'm out of questions for the time being :D

OK

and, that's a wrap for today's chat

the next one is tomorrow(!) at 8:30am US Eastern

Three in a row

Have a good time.

and it will be four on Tuesday

have a pleasant day!