Tarks

Is there anything similar for Civ IV? So many top tier mods break after a while due to the same memory issues.

You only think it's performative because you think people are signalling

You're correct that I think something because I think something else. You're assuming I'm unwilling or unable to tell the difference.

I don't see a betrayal to state that I think it's a shame that people that have copied a performative action, gotten nothing out of it and are then hesitant to try again because they feel they've already tried that avenue and had bad results. It's the same feeling of sadness I get when people have tried therapy, for whatever reason haven't gotten much out of it and then write it off as a sham.

I do get that you're saying 'aha ! I've detected your true intent through my clever analysis of your language' - consider your assumption "You only think it's performative because you think people are signaling. They're not"

They're not? You can state absolute facts with confidence about the people I've experienced in my life that you don't know anything about? That is either some amazing superpower or regular old conjecture.

It might help you to notice how many times I said I think or in my opinion, and how many absolutes you're willing to state.

My take is you've got the right reasoning but the wrong conclusion, I agree with your contextless definition of vulnerability and with the use of it in this context, vulnerability makes people vulnerable, by definition.

From my experience, the reason you'd risk being vulnerable is there are some things you can't achieve without doing so, it'd be like trying to do surgery with a scalpel on someone wearing platemail, or trying to detect radiation with a Geiger counter behind 20 meters of lead, for some tools to work properly they're required to be in a position where they're 'vulnerable', like eyes.

I think it's sad that performative emotions & vulnerability seem to be a popular thing to have to signal for acceptance. Which in my opinion is worse than nothing as at least when you're not faking something it's easier to agree that you haven't really tried it.

Plus rarely survives requirements/context changing because most abstractions are leaky.

My favourite frameworks are written by people smart enough to know they're not smart enough to build the eternal perfect abstraction layers and include 'escape hatches' (like getting direct references to html elements in a web UI framework etc) in their approach so you're not screwed when it turns out they didn't have perfect future-sight.

ha wow, read about a guy having to clean up after some data scientists that'd figured out how to use circular references and an iteration limit to do crazy, hard to replicate stuff, (thankfully) never ran into it myself but I bet that was a 'fun' time for you !

Here's to hoping we both never have to dip back into that world again :D

Shhhhhhhh.

Do you have any idea how much I made in Fintech converting spreadsheets that'd exceeded the TA's ability to hack/keep it all in their head and/or quit?

Favourite included a single cell that had, I am not kidding, something like 150+ nested if statements.. and there was a dateTime bug in it somewhere :D

A friend did very well positioning himself as a data engineering consultant that could come in and quickly improve poorly thrown together data pipelines, wonder what the equivalent is for these :)

Also have to hard disagree. I remember going from the Oculus DevKit2 to the Vive, seeing the change in people we'd invite over for "I'm done trying to convince you with words just Come over and try out VR" evenings.

6DOF, even when sitting, is a significant difference. Your brain immediately feels far more at home with good 6DOF.

Fun fact : one week I spent about 5-6 hours every evening playing Elite Dangerous in VR. Mining asteroids while listening to lofi cyberpunk and pretending that mining was my whole life, it was great. Until my partner would bop me on the back of the head ^_^

About 10 teams, some horizontals like Ops, commercial, design, tech, finance, some product specific KPIs & 2-3 project based teams.

I'm going to need to push to keep the number of KPIs down but 5 per horizontal is reasonable.

ty, not reinventing is the purpose of my post :) I've explored using PowerBI a bit, it doesn't seem to be geared towards extracting the data once it's in PowerBI. I'd want to be able to query the data from other services, for example grafana so that we could set up alerting. There doesn't seem to be a clean way to do this, all I could find was https://learn.microsoft.com/en-us/rest/api/power-bi/datasets...

The escape hatches were one of the first things I used to explain why I initially liked react, called them exactly that too.

"They're smart enough to know they're not smart enough to build perfect abstractions, so they do a great job but leave escape hatches just in case"

Which is very likely referencing this : https://youtu.be/qu32fBkiHFE

Agreed, I thought we were past this with the 4th generation of these frameworks, this is like knockoutjs all over again.

The moment the penny dropped for me was when I read something like this about React:

"We realised that inventing our own Yet Another Binding Language that was less expressive than javascript was harder and worse than doing the work to put the relatively simple HTML constructs into Javascript"

A lot of young companies are hindered by the pain and overhead of developing and supporting multiple native apps (including patching, tracking & resolving separate bugs etc), spending their precious resources on solved problems rather than user-centric things like better understanding the users by rapidly improving the app and getting feedback etc.

Picture a maybe-for-legal-reasons-theoretical app that needs to be supported on android and iOS plus would massively benefit from the ability to preview the mobile app in a supporting Web portal.

PWA gives us :

- A unified codebase across 2 apps and a Web portal (same project produces the ios, Android and web builds, reuse of css styles, UI components etc)

- Significant reduction in effort developing and maintaining 3ish separate codebases for the same functionality (not quite 3x reduction, there are platform specific issues you have to resolve but still really great).

- Way easier time resourcing the project, one skillet for the 3 frontends and the team can swarm to the required work (This was amazing in the current high demand market)

- Access to the huge array of existing libraries and UI components

For larger more established companies then sure go native. But for companies that have to efficiently use capital, any money spent basically building the same thing twice is money not invested in further understanding the user's needs and improving their experience.

That implies you'd dislike this more than most because it prevents "breaking" things efficiently by intentionally crippling tools and throwing out red herrings.

When I see apps going Electron to me they're saying "I care more about making this easily available and focusing on features other than performance" - which is absolutely fine it's a value statement.

Electron likely helped Sabaki focus on other features with good enough performance, while being the best looking and most skinnable Go app by a country mile (I created a How to train your Dragon skin to temp my partner into learning Go :D)

Only so many hours to dedicate to a project, you have to pick what you value most. This comme T is partially because I'd hate for the people involved with Sabaki to not hear that at least some of their users "get it" and love it.

Bryan's amazing talk on this nails it for me https://vimeo.com/230142234

Bought a Corsair K95 a year or so ago and it's fantastic for me, even bought a second for the office. Pricey but it's worth it.

My vote for Lucid, got my company to switch from Draw.io. Nearly everything works how I expect it to which is just not true when it comes to the other online diagram tools

For anyone interested I did a fair bit of research into how I could step into the passable home espresso / coffee game as I WFH a lot.

Given that :

- I make at most 3 coffees a day, usually 1.

- I prefer espresso

I found the traditional options lacking. I'd need:

- a machine costing about £600

- a solid quality grinder.

- machine needs 20 minutes warmup minimum before you can pour a consistent shot (or you need to leave it on).

Instead I thought I'd go a different way and build an all manual espresso setup, using getting past the largest price tag using one of these :

https://www.flairespresso.com/. Takes some getting used to but I've been very satisfied with the quality. You NEED to pair it with a high quality grinder to get solid results (I'm using https://coffeehit.co.uk/products/lido-e-travel-hand-grinder).

Downside is I can't steam milk unless I break out my stovetop milk steamer thing ( https://prima-coffee.com/equipment/bellman/50ss ) but that's fine as I prefer black coffee, the steamer gets more use by partner for her hot chocolates.

My setup : https://i.imgur.com/6M9AT4O.jpg

Typescript has overall been a godsend on larger frontend projects. I'm replying more to add to the public thought and support of it.

Ha, total opposite, our small company has near 100% conversion from greenfield to ongoing maintenance contracts, some days this is a point of pride AND a cross to bear :)

It can take minutes to remember/read my wiki notes on a project if I haven't seen the code for months but the alternative would be to stop trying/learning new things on new projects.

It's a mean cat. In the last few years I've ended up going through cycles of doing a react project, moving on for some months then another react project. Each time I've come back I've been impressed with the changes and they've often improved parts of react I'd previously found wanting.

It encourages you to first understand and say what you need, then talk about what you want as one possible solution.

We're very "good" at solutionising what we think we want rather than what we need. One of the things I took away is a way to clearly consider and express the root cause of something. In the DJ example not wanting their partner to go may be due to any number of reasons that aren't clear to the DJ, they could be lonely, feel insecure, feel mistrustful of fidelity, feel ashamed at their own lack of passion for an activity etc. Any number of these things can come to the surface when you start saying why something bothers you rather than the first solution your brain offers up, plus it's a much nicer conversation when both parties are involved in building the solution.

What's also nice is I've had better "shower conversations" with myself to figure out what I really want from situations.

As a recent 30 year old dev in London looking to do just this, I'd really appreciate any advice :)

I am not interesting enough that anyone will come for me specifically anyways.

No single raindrop believes it's responsible for the storm.

They don't care about you specifically, if you can profile people accurately they have a much easier time of adjusting perspectives for your own aims. You've likely already seen the results of this with the latest American election.

It's gone far beyond getting you to buy more music and they're just warming up.

With TS do I have to have a spec for every third party code or can I import something and use it as-is, but not get the benefits of TS on that part of the code?

Not appropriate but I am absolutely stealing this thankyou :)

Can I call you someone that's invented a zero-sum scenario and is getting annoyed at their own misconception?

You contribute and therefore probably benefit OSM, you're using a google captcha enabled site so you're benefiting from something on that site, that site benefited from the captcha service because they didn't have to write one themselves so could spend their time improving the site you're benefiting from.

You're a link through which google captcha is benefiting OSM :)

"Cyrus explained softly to Adam the nature of a soldier ... He told his son of the sad dignity that can belong to a soldier, that he is necessary in the light of all the failures of man - the penalty of our frailties"

They exist because humans and our current behaviour are flawed, we haven't found better conflict resolution techniques.

The sad truth of this world is nothing is yours unless you can protect it. I know the reply button is right there but please stop spouting rubbish.

Hehe wow it's funny to see my words written by someone else, I've come out of the other end of this, for three months I'd be surprised to be alive in the morning after nights of wakin up to chest pains (when I was 22 and relatively healthy). Like everything it can change you, it gave me a different way of seeing the world and I can slip back into that cold mindset to consider things when I need a bit of distance. It also gave me even more appetite for doing fun things and staying true to my natural, childish disposition :)

I'll never forget the ceiling of the apartment I spent so many nights waking up in pain seeing, or the sun shining on the wall in the mornings as I thought "oh, I'm alive!"

Best of luck to you too friend.