So following from this rant:
https://devrant.io/rants/618679/...

Warning long rant ahead

I resigned and my last day is tomorrow, I've released the app updates a week ago, patched a couple bugs for iOS.

My boss and the idiot who can't open an email on his phone go off to use the app as part of some training thing for the company.

I got a call yesterday saying the Android app has issues and I proceeded to ask my boss what type of phone they have:

"Samsung and Huawei"

I thought okay I need more info "what type of phone..." He responds with wouldn't have a clue....

I can't see the phone, didn't get a screenshot or anything like that but I'm expected to just know what the phone is.

My boss goes on to say yeah it's the app (he is literally the most computer illiterate person I could think of aside from guy who can't open emails on phone, how the fuck do you know that?)

Me: "From all the testing I've done the app works"

Look if you want a more robust error free update hire more than one developer I can't test every single fucking use case to determine the app is 100% bug free, I've tested on at least 10 phones before releasing the update just to be absolutely sure I got everything done and okay I missed something.

So I proceed to get my boss to tell the guy who has the issue I'll sign him up to the testing app to find out the cause and hopefully fix the issue, I setup crashlytics send the email and get a call from my boss saying the guy didn't get the email.

Well okay is it my problem that we have two emails for the same person where one of them is a typo? No it's the guy who asked and wrote down the email instead of actually forwarding a blank email from him to be absolutely sure, I sent the email to both just to be on the safe side.

I swear if he is another idiot who can't open emails on his phone well I can't help him, app works on my phone and the phones at work.

I need a phone where it doesn't work so I can get a solution I know works but if I have to deal with these idiots that can't even check an email how the fuck do I do that?

Sorry about the formatting just needed to get this off my chest before I start work.

Oh and I get asked "so who'll fix the bugs when you're gone" well I can't (in reality I'm not working for free, I'm not traveling 1 1/2 commute time to fix one bug for free, go hire someone you think will love to work for minimum wage and let's see if this guy can do what I did)

(Follow-up to https://devrant.com/rants/2049733)

Went back to that bar today that I had a fight at about a month ago. Asked about that flash drive I lost there, yada yada.. bar owner gave me her part of the story. Apparently she didn't find that flash drive. So that still leaves me to refresh the keys it stored I guess.

"So you got pretty drunk here, had a ton of Duvels, went to the toilet, and barged out all of a sudden, followed by that incident. But you sat for so long in there.. it was suspicious."

Meanwhile I'm here like "yeah yeah that's what happened, that how I recall it too.. but suspicious? Did she think that I was hacking shit from there?"

"I thought you were taking drugs in there."

".. Oh. ... Not to worry, I don't take drugs."

In reply to:
https://devrant.com/rants/3957914/...

Okay, we must first establish common ground here. What do we understand about "showing"? I understand you probably mean displaying/rendering, more abstractly: "obtaining". Good, now we move on.

What's the point of a front-end? Well, in the 90's that used to be an easy answer: to share information (not even in a user-friendly way, per se). Web 2.0 comes, interaction with the website. Uh-oh, suddenly we have to start minding the user. Web 3.0 comes, ouch, now the front-end is a mini-backend. Even tougher, more leaks etc. The ARPAnet was a solution, a front-end that they had built in order to facilitate research document-sharing between universities. Later, it became the inter(national) net(work).
First there was SGML to structure the data (it's a way of making it 'pretty' in a lexicographical way) and turn it into information (which is what information is: data with added semantics) and later there was HTML to structure it even further, yet we all know that its function was not prettification, but rather structure. Later came CSS, to make it pretty. With its growing popularity, the web started to be used as a publishing device.
source:
https://w3.org/Style/CSS20/...

If we are to solely display JSON data in a pretty way, we may be limiting ourselves to the scenario of rendering pretty web pages using aesthetic languages such as CSS. We must also understand that if we are only focusing on making a website pretty with little to moderate functionality, we aren't really winning. A good website has to be a winner in all aspects, which is why frameworks came into existence, but.. lmao, let's leave that to another discussion.

Now let me recall back my college days.. front-end.. front-end.. heck, even a headset can be a front-end to a pick-order backend. We must think back to the essence, to the abstract. All other things are just implementations of it (yes, the horrendous thousands of Javascript libraries, lol).

So, my college notes say:
"Presentation layer: this is the UI.

In this layer you ask the middle tier for information, which gets that information from a database, which then goes back to middle tier, back to presentation. In the case of the headset, the operators can confirm an order is ready. This is essentially the presentation tier again: you're getting information from the middle tier and 'presenting it' as it were.
The presentation layer is in essence the question: how do I bring my application data to my end users in a platform-and solution-independent way?"

What's JSON? A way to transport data between the middle tier and the presentation tier. Is that what frontend development is? Displaying it in a pretty way? I don't think it is, because 'pretty' is an extra feature of obtaining and displaying data. Do we always have to display data in a pretty way? Not necessarily. We could write a front-end script (in NodeJS perhaps) that periodically fetches certain information from a middle-tier is serves a more functional role rather than a rendering one.

The prettification of data was a historical consequence of the popularity of the web (which is a front-end) (see second paragraph with link). Since the essence of a front-end is to obtain information from the back-end (with stress on obtaining), its presentation is not necessarily a defining characteristic of it, but rather an optional and solution-dependent aspect, a facet.