HackerTrans
TopNewTrendsCommentsPastAskShowJobs

Xeago

no profile record

comments

Xeago
·2 miesiące temu·discuss
For me the nail in the coffin will come in 2027Q1: with CodeWithMe going away. Until then, the quality of editing code remotely together with the mostly clean refactoring and navigation options is a deal breaker.

If anyone has something roadmapped to replace CodeWithMe, it's worth bucks.
Xeago
·5 miesięcy temu·discuss
What about an alternative business model, pay-per-date? There's an application in NL that charges €7.50 to arrange a dinner, disallowing chat until 2 hours before the arranged date for practicalities. They partner with restaurants and you each get a 'free' (you paid for it..) drink; but with the commitment that your date also paid for it and will therefore show up.

This removes a lot of the meat-grading and endless swiping; with the platform prompting you why you're not working to scheduling your existing matches. Whilst I have no experience with the absence of any scheduled matches, this gives the platform insight into whether you're a worthy date (remember, each date is profit!).

One date on tinder/hinge/bumble in a 5+ years to a finding my partner in a few months. Paying for the actual date experience was so much less and so much more fun than the footing the subscription on the other platforms - even accounting for the cost of food.
Xeago
·7 miesięcy temu·discuss
Echo'ing similar interest with a similar scenario; but would also be much interested in other forms of media, such as screencasts or demo projects with an accompanying show-case document.

Reading the release notes of the sdk and/or the MSDN pages used to be a great resource, and probably still is, but it's difficult to find new gems.
Xeago
·11 miesięcy temu·discuss
I concur. There was supposedly a migration path from their postgresql image & chart to the postgresql-ha image & chart.

Aside of having to re-mount the data disk and move things around manually; the -ha chart has numerous other issues where it always requires the master to be node-0. And with pods being rescheduled within a statefulset, good look having the master be on node-0. If there was an outage and the master is anywhere else, node-0 will just 'wait' for a master to come online, time out and shoot itself in the head thinking it is in a network partition and that retrying may help.

The algorithm implemented by postgresql-ha turned out to be plain broken. Only able to survive pods neatly shutting down.