blöder papst, hat mein quiz geklaut.

uuh zehnforwärts-kreuzüber, wie viele wir davon wohl sehen werden, dutzende, hunderte? unmöglich zu sagen.

not a course but a book Eloquent Javascript, especially chapters 13 to 19.

The Book is about plain JavaScript and a big chunk of it is about javascript in Websites.

• spent time to generate/optomize your indexes.
• faster storage/cpu/ram for your rdbms
• get the data needed by specific services into the service, only get the data from a central place if you have to (spinning up a new instance, another service changes state of data you need, which is a warning sign in itself that your architecture is brittle…)
• faster storage/cpu/ram
• generate indexes
• 2nd level cache shared between services
• establish a faster datastore for often requested data thats used by multiple services (that might be something like redis, or another rdbms on beefier hardware)
• optimize queries
• generate indexes
• faster storage/cpu/ram

Amsel noch pepps?

ich kenne deine socken-pfosten, ich sehe keinen Grund dir nicht zu vertrauen :D

Umarmung einer größeren Person, hat mich aber auch 10Minuten gekostet das zu sehen.

Rasuren außerhalb des Gesichts führen bei mir immer zu eingewachsenen Haaren und juckenden Rötungen, ich erwarte also bald Profitipps!

hmm

• ich schau manchmal Zuckung
• ob ich im Ruhrgebiet lebe ist Auslegungssache
• ich weiss was pog ist.
• ich verstehe das michmich nicht.
• wann gibts eigentlich ne neue Staffel vom Habgewesen Hotel?

no, i don’t think there is a big difference in ‘difficulty’ between both languages.

there is just more material for java, and as i said the languages are very similar, so learing to program in java wont be a waste of time if you plan to only use c# after that, because the concepts you learned a long the way will easily carry over.

learn java, way more material for that, but conceptionally very similar to c#. I suggest a book like “Head first Java”.

after that c# will be much easier to grasp.

i mean: provide a link to the repo in your posts body, do not just link to your blog ;)

it would be a good start to include a link to a git repo in your posts, when you share your blog posts.

if your code is hosted somewhere where you can create issues and tag them, create issues and tag them as “contribution welcome” or “good first issue”.

github is probably the best plattform to get contributions, simply because it’s the biggest and so many people already have an account there.

but complex reworks or new features are probably nothing a random contributor will provide, but you or close collaborators.

“Domain Driven Design” by Eric Evans, aka the blue book. It’s very dense however and very object oriented, but concepts apply even if you dont work with object oriented languages, you might have to do more footwork to get from a domain model to services that adhere to the model.

“Head first Software Architecture” might be an easier on ramp and touches on simmiliar concepts.

yes, this is exactly what you have to think about. the left example even aknowledges that deadlines for “tasks” might be different from deadlines for “payments”, which suggests that the abstraction is not “clean”.

“logs show a reoccuring error in layer 8 everytime a subset of users engages with the system, reassigning this to the service desk to gather more information.”

i’ve read that on real ticket, i’ve laughed about it. it also makes me glad that i don’t do customer support, i don’t have the patience to keep explaining the same people that they keep doing something wrong and i lack the diplomacy skills to engage with devs that believe to be infallible and pretend that bug reports are personal insults against them.

because no one follows the damn guide and “scrum” is done so managers can claim the company can work “agile”, because customers dont want “not agile”, customers also dont want to participate in the way it would be necessary for a project thats supposed to follow the scrum guide. that also sounded good for people looking for a new job so hr wants to put that into job descriptions and now everything is scrum and agile and i still have to sneak in refactorings or have to fight to get time to work on our fricking ci pipeline or need to conspire with QA to get them time to work on test automation, because screw the notion that decisions should be done by the people doing the work.

screw “scrum”, and the word “agile” should never have been taught to anyone claiming to be a “manager”, we don’t need managers we need people helping us getting the tools we need and trust that what we do, we do to deliver better solutions and helping us to fascilate constructive exchanges with customers.

data-plumbing-for-corporations tends to be able to be done in a way that’s easily testable, but also most people get paid to bolt on new shit onto old shit and spending time on “done” code is discouraged so once they fall behind on writing tests while developing the new shit those tests will never be written.

and bad developers that won’t write tests no matter what actually do exist.