HN user

shnkr

31 karma
Posts2
Comments29
View on HN

God's work. Simple process but didn't find a matching profile to apply - boring backend principal engineer with 10+ yoe.. will keep an eye though.

NO certificate or authority, I'm a nobody.

Take LinkedIn as example, and the messages from recruiters inviting for an interview. Why can't they get the profile checked by hiring managers and send out an offer directly? Once the candidate accepts it, collect the documents and run background checks and deny if there is discrepancy.

Whatever may be the end goal, MITM is called an 'attack', not 'research'.

I'd not last a single day at such a company who would ask me to do such things. I had worked for a national political party in IT and left the job once I found about it corrupt practices and scams.

If we, as engineers collectively upheld ethics as part of work culture, Meta wouldn't have attempted it.

The relationship with commercial vendors isn’t always healthy, but many major OSS projects are supported to a significant extent.

Almost always the so called "community" supporting a OSS project is an employee of a commercial vendor who is only interested as long as he is assigned to the project or task.

The solution is to have a full time owners and maintainers for all the critical projects and the government has to foot the bill. The govt can setup a division to identify such projects.

insert meme *Don't give me hope*

In an idealist world, you're the perfect employer and I should be your employee. I want to believe that these employers exist but my conventional wisdom says, they are just textbook version, real world is different.

A little bit about me: In my 12 yoe (still at same place with steady growth), worked 6 years for one team, built a framework. one SE was dumping his new projects and moving to fresh ones while I get to maintain them, soon moved to different team. I stayed, maintained, stabilized, scaled, tuned, left only after then to different team (actually I'm the only one) to work on a new product. Again same situation, many have joined and left, few after 1 year and none of them contributed anything significant to the product. None of them cared about the product or the company, just optimizing for their career and pay. But then what's the passion in it if you don't care about what you've built and make it better.

I'm now pivoting to new team (don't know yet) planning to build something again from scratch. I'm optimizing for my passion, but some where deep inside I'm worried about my future prospects because of long haul.

there are two types of people. 1) who trusts everything on the internet 2) who doesn't trust everything on the internet.

whether its free or premium, the second group still wouldn't trust the search or ai results. they apply their own due diligence. sadly it makes a tiny percentage of the world people now. we should strive to increase this number and in next decade or so, mostly it happens.

my question was specific to databricks model. If it followed llama or openai, they could add a line or two about it .. make the blog complete.

GenAI novice here. what is training data made of how is it collected? I guess no one will share details on it, otherwise a good technical blog post with lots of insights!

At Databricks, we believe that every enterprise should have the ability to control its data and its destiny in the emerging world of GenAI.

The main process of building DBRX - including pretraining, post-training, evaluation, red-teaming, and refining - took place over the course of three months.

Disclaimer: Author to a competitive k8s backup solution.

I personally don't think Velero is a solution for production workloads or anything serious. Only an established backup company/devs will have expertise to implement and handle all cases and take care of all data loss scenarios. Ideally k8s authors should have stopped at providing a tool (they have snapshots like any db/fs) rather than writing their own backup piece. Unfortunately many of the industry solutions are wrapped over Velero except a few (two?), one I implemented from scratch for Commvault.