hanifbbz

This is a free open source privacy first app that you can either run locally or as a Chrome Extension. There's so much data that you can practically reconstruct LinkedIn (profile, network, jobs, messages) and more (IP addresses, private contacts, etc)

Here's a visual post for using LM Studio and VS Code (and Pi): https://blog.alexewerlof.com/p/local-llms-for-agentic-coding

One way or another local AI is the future. I actually find weaker models more interesting because it keeps me sharp (at the cost of velocity of course).

WTF is this?! Sattire? AI generated propaganda? I honestly don't get it. Can OP elaborate why it's a good content worthy of people’s time? Thanks in advance.

Is this available as open source anywhere to try?

A pragmatic definition that helps distinguish between resultant, weak, and strong emergent properties in interactive systems, LLMs, and incidents.

Interesting stats.

The accompanying article explains how it works: https://blog.alexewerlof.com/p/local-browser-ai

And the source code is available at: https://github.com/alexewerlof/local-browser-ai

I like how the landing page (and even this HN page until this point) completely miss any reference to Meta and Facebook. The landing page promises privacy but anyone who knows how FB used VPN software to spy on people, knows that as long as the current leadership is in place, we shouldn't assume they've all of a sudden became fans of our privacy.

That's ~120 second of life spent reading minutiae (plus 15 sec writing this). And wasting random reader's time at scale. This is uniquely British.

Could you be more specific about which book and chapter talked about this problem and how the solution was different or similar?

What's the ublock block thing?

IP is IP. LLM vendors are in legal battles with all sorts of IP owners. Putting it explicitly there (as awkward as it is) creates a legal obligation where the company or individual that fed it to "AI" cannot deny: "oh! I didn't know, therefore it's not stealing"

Please elaborate

I don’t know. With the advent of AI-productivity tools (regardless of where we stand in how much the actual boost is), EMS should be able to offload part of their admin work and devs should be able to deliver more and faster. Long way to say that I'm skeptic if those numbers still apply in modern or near future environment.

The article describes insight on how to gain leverage. Regardless of promotion plans, it's good to have leverage in the current economy so your career doesn’t end prematurely when the company goes to cost-saving mode.

The tutorial itself is next level with stunning interactive visual story telling.

It's a common pitfall to measure what's easy. OTOH, the calculations can be quite arcade and hard to relate to. Many observability platforms have something in place but they leave more to be desired.

Service Levels can be quite simple at a high level but as soon as you start implementing them, the calculations can quickly become abstract and hard to understand.

Yes, that's the inspiration. The difference is that this one generates a link (rich or plain text) that can be put in a web page. It doesn't require the audience to have bookmarklet installed.

This post itself was generated using the web app.

Use case: Putting a link in your pages (e.g. blog posts or newsletters) to make it easier for your readers to share it on Hacker News. It is open source.

Good summary of the book.

It's true that many businesses which build software have no business writing software.

To keep the committee alive, it expands scope, recruits more people, and assimilates their mandate to the hive. Internally it feels like a grass-root movement on the rise. In reality, it’s about repurposing an expensive tool (recurring meetings with high-pay participants) for every problem. It may even emit some manifesto or generic vision and mission at this point.

One leg of the problem is the environment that allows the committees continue way past their expiration date. How can they get away with it?

Amazon layoff caused a lot of uncertainty internally. Inflation made some people work extra and some picked a side gig. Turns out the percentage of people who think they are being monitored is less than the managers who do monitor them! Meanwhile tax-breaks and municipalities have a say in forcing the employees to come back to the city.

The article is in favor of hybrid work but with a policy that doesn't back-fire with attrition of top talent and hurting the economy long term. There's also one example RTO policy.

Story from a job I had couple of years ago. At the time I took it for granted but I haven’t seen something quite like it before or after.

"Remember who you were before the layoff and remind yourself of that success when you feel the imposter creeping in."

Author here. I do hire staff engineers these days. A few points:

1. Spotify is a Swedish company with a strong brand identity. Conformity culture is a bit strong, so I can totally understand why they would want "someone like us" than someone who would ask the challenging questions. That's my take on that interaction but maybe I didn't write it well. I edited the article a bit.

2. Staff is a leadership position and like other leadership roles, the impact of your personal belief will not stay at the individual level but rather spread. A positive attitude pays dividents. In that particular example, I went in with negative prejudice. The right interaction would be to have an objective argument and share their view as someone who bought into it and is working at the company. The least they could do is to use that as an opportunity to set the record straight. At least that is what I do if a candidate asks the hard questions. I don't have to convince them, but I'll do my best to honestly answer it and quite frankly maybe I learn something about the company I'm presenting that I didn't know.

Would be fun to sit in the room where they motivated it: "we need a kick ass office to hire the best talent to be able to maximize the ..." I don't know where I was going with this! I have no clue how they got away with it :D

In this particular case I guess questioning the business model of the company by bringing some controversy on the first interaction wasn't very strategic. Maybe the staff engineers they have hired don't do that!

Good to know. Thanks for sharing.