3,593 karma · joined July 30, 2007
I'm applying multi-agent reinforcement learning to AI Safety. I want to ensure that Artificial Intelligence will benefit human society rather than hurt it. I'm addressing both short-term consequences of existing AI tools such as LLMs and long-term existential risk imposed by the potential development of Artificial General Intelligence.
I propose to solve the problem of AI Safety by improving the social behavior of AI agents. Most AI research is focused on getting AI agents to solve bigger and more complex problems in the most efficient way possible; my research is focused on achieving cooperation, reciprocity and teamwork between AI agents.
My strategy is to distill lessons from the study of animal and human societies and apply them to AI agents.
Read more about my research here: https://r.rachum.com
If you're a good developer you likely have developer friends who work for different companies. These can also be people you've collaborated on open-source projects with, or met at conferences. If you've made a good impression on them, tell them that you're looking for a job. Either they'll be interested in getting you hired to their company and getting a reference bonus, or they could hook you up with friends of them who are looking for developers.
Still, I'd like to show a gap in what you said: You talk about what kind of increase in revenue you'd have if such and such people did a better job, and what kind of ROI you'd get from each department.
But the question is, an increase relative to what, or an ROI relative to what?
Let's take the billing department. If you made sales for $10 million, and your billing department works okay, then you would have a revenue of $10 million. If you hired the best billing experts on earth, you still would get just $10 million. So that might make you look at the billing department as a cost center rather than a profit center.
But maybe if the billing department fucked up royally, either by not charging a customer, or overcharging them and hurting the relationship, or breaking obscure laws and getting the company in legal trouble. Then you could be out a lot more than $10 million.
So in effect, you could view the billing department's ROI as "how big a disaster they can prevent, and how good they are at preventing it." That kind of thinking makes sense for any department in the company.
That's the reason why I don't see the logic behind branding some departments as profit centers and some as cost centers.
I'll say it again, I'll be happy to see an objective definition of profit centers and cost centers.
This is as good a place as any to put this:
Peter Drucker originally coined the term "profit center" around 1945. He later recanted, calling it "One of the biggest mistakes I have made". He later asserted that there are only cost centers within a business, and "the only profit center is a customer whose cheque hasn’t bounced."
If they define themselves as a technology company, which I believe they do, and they want lots of complex features for their services, and set an exorbitant valuation on that basis, then they better have the right infrastructure for that.
If the function is launched in a spawned process, it'll work, though you might have trouble getting the stderr, so you better include a log file as the first argument, like this `@snoop('/var/log/snoop.log')`
If the function launches new processes internally... I'm not sure.
If you try it and it doesn't work, open an issue: https://github.com/cool-RR/PySnooper/issues
pdb and its variants (my favorite is PuDB) are generally difficult to use in complex, corporate projects. If you've got a multi-process, multi-thread Python project running on a remote host, you'll need a really full-featured debugger to work with it effectively. I recommend Wing IDE or PyCharm for that.
You can set depth=2 or depth=3 and then you'll get a huge chunk of log. The deeper levels will be indented.
I'm interested in the moral dilemma, especially regarding employees.
Aaron writes: "The biggest emotional investment that founders make – especially early on – is convincing great people to take a leap of faith and accept an offer to work their butts off on a long shot. This dynamic is why transparency around the decision to shutdown and the timeline of it is so important."
Imagine you're a founder and your company is on its last legs. You can make a last-ditch effort to pivot and save the company, but that means that if you fail, which is likely, your employees will get shafted. Can you really communicate this transparently to your employees, and risk having them start searching for a way out, dooming your chances to succeed in turning around the company?
Hi, I'm Ram, a freelance web developer with six years of experience building web applications for startups.
My expertise is in taking your idea and building it from scratch to the point where it's a fully-functional web app that serves paying users.
Technologies used: Python, Django, Heroku, Git.
More information: https://chipmunkdev.com/
"As recently as 2005," heh. In the frontend world, you might as well say "as recently as the Paleolithic age."
Maintaining relationships with different kinds of people is work. It's hard and meaningful work.
> They have figured out that there is really no job security, and they could be one layoff wave away from unemployment.
There most definitely is job security. Some people have lots of it, some have very little. There is no 100% job security, if that's what you were hoping for.
> They have figured out that its much more about face time and spending long hours at work rather than actually being productive.
Again, spending time with people in a social environment is a meaningful thing to do with one's life.
> They have figured out that the majority of their work, to their surprise is not actually that important or necessary.
It's not surprising that the majority of the product / code is not that important or necessary. If you are a good teammate, you might be an important or necessary part in your teammates daily lives.
> They have figured out that its important not to take too much vacations, because its an opportunity to loose the little work they have to someone else.
"many", "lose", "it's". I'm pretty close with my teammates, and I've never heard of any of them giving up any of their vacation time to get respect from our boss.
> They have figured out that they are never going to get payed the true value of their work, and that is almost the definition of being an employee.
I think that you if you'll try to give a definition of what you call "true value", it could be reduced to an absurdity.
> They have figured out that its all a system of serventry not too different from the medieval relation between master and servant.
I wish every person that said that would get to spend a couple of weeks as an actual slave, and would then report on their impressions.
> They have figured out that its a system that they are being grinded through and discarded, and that they are condemned for life to making someone else rich, never getting a chance to trully fulfill their dreams and ambitions.
Anyone wants to take on this one?
Really? A private company deciding not to do business with you feels like your basic human rights were taken away?
"After emailing AirBnB support and its founders multiple times, I’ve finally given up."
I've had a problem in Windows on my computer the other day and emailed Bill Gates, could you believe he had other things to do except respond to my problem?