firstbabylonian

It sounds like flogging may be a feature, not a bug, of this system.

A doctor from a local dispensary (recreational cannabis isn't legal where I live, but medicinal is comically easy to obtain) once told me:

“What do you do? Ah, a software engineer. I guarantee you most people in your industry are on it all the time.”

He paints a picture where every highly functional modern worker these days is on a steady diet of CBD and THC products, perfectly calibrated to fit their lifestyle and the demands of their profession.

Thinking about it, this might explain some of the odder Zoom/Slack interactions you may have with colleagues at work.

In Russian, you do hear people say «что будет, то будет» — literally ”what will be will be”.

The formal rules of the language discourage tautology though. It's considered ineloquent, so it's not very common.

https://restofworld.org is a good place to start.

> telemetry can't tell you the value of any work you haven't done yet

But it can allow you to extrapolate from the value of things already done and usage patterns around them?

AI is not human children.

How do we go about passing this kind of historic knowledge between generations of engineers? In my observation, most newcomers to the industry are trained either academically or through self-guided practical learning, i.e. by hacking and reading tutorials. Neither method exposes them to such 'contemporary history' of innovation within the field.

> I've found that Eastern European developers generally believe they are the best (even when they aren't)

I've been this Eastern European developer and seen others. A 100% accurate assessment. I'd go as far as to say that this animalistic bravado must not be encouraged.

Ultimately, it comes from a place of poor self-awareness. There's something about EE cultural/historic context that breeds a lot of brilliant zombies.

So as with all un-self-aware team members ([1]), EE developers with these traits can have a serious detrimental effect on the culture, unless kept in check. My suggestions:

* Call them out on toxic behaviour, so that it doesn't become normalised.

* Make them directly accountable for their work. EE devs relish the idea of being a shadowy IC of outsized but unacknowledged importance. Don't let them mythologise their own status.

[1]: https://hbr.org/2018/10/working-with-people-who-arent-self-a...

Regular people don’t realise or care, they just want to be where their friends are.

What if a native application (mobile or desktop) wants to consume the API?

Fair enough. Would you consider officially endorsing any such projects (e.g. with links on your website), for mutual benefit?

Do you have any plans to support (and accept contributions to) non-English books? It’ll be amazing to see original Russian classic texts redone with the same level of care.

A lot of iOS build automation tooling is dependent on Ruby. fastlane is the de-facto standard in this space, which is a Ruby gem and CLI application. As a result, every iOS developer almost inevitably has to learn at least some basic Ruby to cobble together a deployment pipeline for their app.

Someone I know runs their entire life on Trello. It's their digital brain, organised into a fleet of boards. Some of them serve as archives of various documentation and snippets of valuable info. Others are for tracking active projects, current engagements, etc.

Trello is flexible and simple enough to work well in a number of different capacities, so it's a great multitool for some. Especially if you're naturally geared towards organising your life in this methodical kind of way.

Apps are not food.

> Ticketmaster doesn't take a 30% cut on consession sales at the event

Ticketmaster doesn't provide as complex of a service as Apple does with the App Store.

yeah, right, so what do you call such a type? I believe that is the actual question.

a zip bomb?! that's sabotage

I agree with this. 'Technical debt' always exists in the heads of the engineers: the rest of the organisation can't see it. It's an invisible problem, imagined by the engineers, and not always in touch with the practical long-term reality.

Software is a tool. Tools that are used often require maintenance, which in itself is not a novel concept.

Whereas saying 'technical debt' is like delivering a dramatically vague House MD diagnosis.

If you must, call it what it is – Maintenance – and let's move on.

Are there any open source libraries that implement this in practice?

Apple has no reason to care about UNIX philosophy at this point at this point though, do they?

> One important lesson I've learned in my career is never to run your own observability platform if you can afford for someone else (whose entire product is observability) do it for you.

Why is that?

That’s a typo.

The pronunciation is close to “dee-yet mah-ross”

Is this based on any historical data beyond the 20th century? Because the 20th century is not necessarily representative of the "standard" human nature. With all the wars, rapid technological advancements, globalisation, etc., we have created a different environment and different kind of people.

> Why does one need the "fastest phone"?

We shouldn't need them, but we do, because the quality of consumer software is very poor these days. To enable "rapid" and "agile" development, where "customer value" is delivered "continuously", developers write under-optimised, resource-hungry software that never gets refactored.

but isn't it surprising that such a strict subset is maintained across all life?

while others??

at a certain evolutionary point in time?

Love the idea! In my teenage youth, I had two interests: writing fan-fics and coding up websites in HTML. Somehow I felt that the only way I can "trust" my writing to look correct is by live-coding it in HTML as I composed it.

Nowadays, I still write, and I use Markdown like you are "supposed to"… But it does never feel quite right.

Live a little!