Anyone else have that kind of manager who you ask a simple, single sentence question of, and get a ten volume essay of a response back from?

How do you deal? I'm usually a very capable, independent and initiative driven person but holy fuck.

All we need here is a:

"Hey manager, you assigned me this thing. I'm wondering what we should do about this particular edge case I've seen a few times in past roles?"

and a

"I'm not sure. Check with Steve, he should know, as his team worked on it and did x, y and z. If he doesn't know, come back to me"

and we're done.

Instead I get the entire Lord of the Rings saga written in zalgo.

This was originally a reply to a rant about the excessive complexity of webdev.

The complexity in webdev is mostly necessary to deal with Javascript and the browser APIs, coupled with the general difficulty of the task at hand, namely to let the user interact with amounts of data far beyond network capacity. The solution isn't to reject progress but to pick your libraries wisely and manage your complexity with tools like type safe languages, unit tests and good architecture.

When webdev was simple, it was normal to have the user redownload the whole page everytime you wanted to change something. It was also normal to have the server query the database everytime a new user requested the same page even though nothing could have changed. It was an inefficient sloppy mess that only passed because we had nothing better and because most webpages were built by amateurs.

Today webpages are built like actual programs, with executables downloaded from a static file server and variable data obtained through an API that's preferably stateless by design and has a clever stateful cache. Client side caches are programmable and invalidations can be delivered through any of three widely supported server-client message protocols. It's not to look smart, it's engineering. Although 5G gets a lot of media coverage, most mobile traffic still flows through slow and expensive connections to devices with tiny batteries, and the only reason our ever increasing traffic doesn't break everything is the insanely sophisticated infrastructure we designed to make things as efficient as humanly possible.

I just used chatgpt and placed bullshit jargon to aid my budget and OPEx for this year, and it worked.

Each year, we formulate some sort of paragraph/essay on how we plan to help the company achieve its goal. I dragged my feet doing this exercise.

Great, more reasons to be lazy.

Great googly moogly is Kotlin an ugly language.

If you are just starting out with Android or Java development in general, I highly recommend sticking with Java and avoid Kotlin like the plague. It feels like a meme language that was taken a little too seriously.

Full of little flowery nonsense that aims to make the language more human, but only serves to make it look like a child designed it.

I absolutely hate when a language doesn't require type declarations.

The "it" keyword rankles my underwear beyond belief.

Trying to build a dictionary/hashmap/hash felt like I was writing out an essay for school. In other languages it's straightforward and makes sense. Even PHP makes more sense.

I am obviously missing something here, because there is no way something so common and done the same way across different languages has such a wildly different approach in Kotlin.

I have as much experience with Java as I do Kotlin but it immediately makes more sense as a language and doesn't have all this flowery nonsense. It is verbose, which means I don't have to decipher what the code is actually doing when I read it.

I'm familiar with the enterprise Java meme, but I'm not writing enterprise Java, and that's not my style anyway so it doesn't affect me. But even so, that would be a million times easier to handle that Kotlin.

Got this design for a button.
Now I'm writing an essay in the ticket about how this is problematic for localization and accessibility.

There are some people who do not want to talk about death. Others will simply talk about it out of curiosity. But sometimes, such a tragic subject can also bring out the best in you when it comes to writing. Let us talk about writing a death essay. This subject can be considered a good topic especially if you do not have one yet.

One important thing that you must know before we talk about the topic is the essay structure. By now you should already know the parts of a formal essay and what their functions are. In any case you need to input the introduction, thesis statement, body paragraphs and the conclusion. Now let us take a look at some possible topic scopes for your death essay.