minaguib

This is more common than you think. So long as you know what you want as an outcome, don't overthink it. Unless you're working with higher-than-average levels of sociopathy, you'll find that you can talk about it and transition to something you find more rewarding.

Also try not to frame it as something shameful/step-down. Individual Contributors and Management are entirely different jobs - clearest evidence of that is what your calendar and day-to-day look like. There's some overlap, but it's a pivot, and that's okay.

(P.S. Stick with the personal trainer and running group :)

Good luck.

This was yanked almost immediately after it was deployed and announced:

https://globalnews.ca/news/9785851/quebec-transport-ministry...

I'm not a frontend dev, but from cursory reading of htmx docs, it seems your example implying every chat message would require sending the full log to every user is a bit of a stretch - a more natural way would be to transmit only the new messages and use one of the "before" or "after" swap settings to insert them where appropriate.

That's EASY

PostgreSQL. The answer has always been PostgreSQL, even at the height of MySQL's popularity and LAMP craze.

It is a VASTLY better piece of software and ecosystem - yet it's boring at the same time - all things I demand from the DB system whether it's a toy project or an enterprise app.

We have collectively taught all the non-tech folks not to enter sensitive information, such as credit card numbers, in non-secure forms that don't show the lock.

This used to mean a lot when certificates were harder and more expensive - the rationale was fly-by-night bad actors wouldn't bother. This is most definitely not the case now.

Realistically as well, it's mostly to guard against man-in-the-middle interception - as we all know once it hits the server handling the SSL termination, all security bets are off.

FWIW Chrome does (and I assume will continue) saying "Not secure" where the padlock used to be, for HTTP sites. So there is at least that as a warning.

Interesting opinion.

I was mentioning the 4000 weeks idea to a friend and how I found it interesting and thought-provoking, and their reaction was quite the opposite as it was way too dark for them.

I wonder if this idea highlights some fairly clear differences in people's personalities and mental models (at least, at the time and place in their life they're evaluating it).

It's interesting that this: > the right thing to do is to give SRE teams the power to say "no" and refuse to take the pager for any particular service

Was a tenet in the original Google SRE material. SREs help operate well-behaving services using engineering best-practices. Services that fail to behave well and bust their error and support budgets repeatedly go back to the teams that wrote them.

Absolutely incredible - from idea to implementation to output.

Hivestack | Montreal,QC,Canada | Hybrid | https://www.hivestack.com/ Industry: Adtech, specializing in Digital Out Of Home

Hiring: Senior & Staff-Level Software Developers, as well as DevOps

Stack: (frontend) Vue|Swift (backend) Python|Go, mix of SQL and noSQL DBs, cloud-native

If you enjoy working on high-volume low-latency systems, please get in touch (info in my HN profile), would love to chat. AdTech experience a plus but not a requirement.

I'm huge fan of DuckDB. Awesome to see a blog post like this describing what looks like a fantastic local ecosystem surrounding it.

Cool material, but happy to have been exposed to okso.app as a (newcomer?) free online sketching tool (a-la excalidraw, a bit...)

Hivestack | Montreal,QC,Canada | Hybrid | https://www.hivestack.com/

Industry: Adtech, specializing in Digital Out Of Home

Hiring: Senior & Staff-Level Software & Systems Engineers, as well as DevOps

Stack: (fe) Vue|Swift, (be) Python|Go, mix of SQL and noSQL DBs, cloud-native

If you enjoy working on high-volume low-latency systems, please in touch (info in my HN profile), would love to chat. AdTech experience a plus but not a requirement.

Interesting. Never tried dgsh before, but yea it looks like my poor-man's CLI workflow for a lot of tasks

I don't know why I waited so long to try it.

I wrangle a ton of raw and aggregate data locally every day. I've had a 10-year habit of massaging via unix CLI tools and pipes then moving to excel. I guess I didn't wanna write code. Funny thing is I love SQL.

But with `duckdb_cli` it's a game-changer. I'm truly truly impressed.

My reading is if you allowed Salesforce/Heroku or Travis CI access to your GitHub account/organization, then there is a chance that that grant was leaked to a malicious third party - and they may have accessed your github account and downloaded private material.

GitHub indicates they are performing an audit and if they find such evidence they will notify each account/org within the next 72 hours.

Absolutely brilliant essay and work - It's always extremely impressive when someone can both develop such depth in an area that interests them but also write/blog so eloquently about it.

This is also a great example where I can perfectly see VR/AR shining and perhaps indispensable in this particular use case.

AFAIK this is how it worked with classical OS packages (think rpm/yum/apt/etc.)

Packages and metadata was all prepared for distribution over nothing more than static file hosting and http(s) to leverage as much existing infrastructure as possible.

+1

Ran into a pathological case where a query that usually took 10-20ms would sometimes, semi-randomly, take > 15 minutes (while the corresponding PG process server-side is running at 100% CPU)

Explain showed a dramatic query plan change, which led us towards bad table statistics.

1. Don't lie to the employer

2. It's an employee's market, so don't shy from applying

3. Don't lie to yourself - if there are strong underlying causes which will affect your work performance, perhaps you're not ready to re-enter the workforce

I'd get in touch with LastPass support asap to see if they have a digital trail to help you figure out what happened.

I'd also guess the most plausible situation would be malware on your computer that managed to sniff your credentials in-transit/clipboard/memory/browser/keyboard and exfiltrate it to some shady folks.

First guess was "black" Second guess was correct It feels too lucky

Damn, your guess sounds quite plausible.

Also, everything is awful.

Don't overthink it.

Do it. Develop the habit, 1000% more important than measured results. Push yourself to do it even if you're not feeling like it, and even if you're not enjoying it mid-exercise.

The net result is you're overall better. Not just physically, but mentally and emotionally as well. THIS is the biggest benefit for me.

I see the author's point.

However it focuses almost entirely on the idea of documents/information retrieval.

The web would not be at today's scale if it focused on written-word documentation. For better or worse, most individuals are spending their time online for entertainment.

Scroll to the bottom, find the llama, click it :)

I've noticed a couple of machines in the gym (pre-covid) got very little use specifically because they're brutal - specifically the jacob's ladder machine, and VersaClimber.

Are you able to actually look forward to an "ass-kicking" workout on daily basis ?

I understand in theory they may grandfather me in if I act now on this limited-time offer.

But screen-sharing, essentially what's on the table to an app on my Laptop, should not require cloud services nor a recurring monthly subscription.

The coupling reeks and has really turned me off my decision to buy.

lolwut ?

Don't consumer ISPs hand out /64s or /48s ?

I was days away from ordering a Remarkable 2, despite the high price.

I could see it being amazing, with screen-share, in diagraming and sharing visually with webex/zoom colleagues.

Now it looks like I'll need to pay them $7.99/month for the privilege ? Instant hell-no.

This is pretty cool, from a "check-in-self-serve-here" perspective.

In contrast, in Quebec Canada, the QR codes are issued to people once they get vaccinated, and contain the person's name and vaccination(s) statuses, and digital signature by the issuer directly in the QR code.

The government then published 2 apps on the app stores: * App for users to easily host the QR code (instead of email/PDFs/etc), but more importantly: * App for businesses to scan the user-presented QR code and validate the signature, to allow into the premises (after also checking a photo ID to ensure person face matches ID and ID name matches name in QR code)

The above is because some businesses, like sit-down restaurants (even if eating on the terrace), are required to ensure patrons are fully vaccinated.

I don't know if the "scan" app also remembers who it scans for contact-tracing purposes or not - but there's a separate contact-tracing app for that, also published by the government, that uses iOS's and Android's contact-tracing facilities.