Are we sure some of that is just cutting costs while increasing ai spend and then falsely claiming ai replaced them? What better way to justify your ai projects and ai spend than to lay off entry level data entry people and junior devs regardless of the success of your projects.
Yeah so most of my friends who are dealing with spike in outsourced devs in their work environments are cleaning up the AI slop churned out by offshore people who are slinging code and getting the business requirements all wrong. Their jobs are now to clean up the mountains of code coming in from people who don't really get the problems they are being asked to solve.
Outsourcing seems to come in cycles, where it's tried, fails due to communication issues (resulting in quality issues), then things get inhoused again.
I do think there is some opportunity for AI to smooth out the communication aspect, but I think what we will actually see is larger volumes of poorly guided work coming through for each feature. The AI does not fix the lack of deep systems understanding which is why inhousing is always the antidote to bad outsourcing.
I need to make this clear, there are great devs on either side of the various oceans, the issue is usually communication between two parties with nuturally mis-aligned incentives.
I’ve had a lot of success in past with the Apple approach. I design and architect locally but build it overseas. I think AI and the post-WFH office work culture really helped executives get over the hump / learn to make decisions and lead without being in the same physical space daily. Also, feel like the communication gap is largely a solved problem at this point. It is incredibly common to find English speakers in this profession from any country. The trick is learning to project management. At times, you simply just give the person objective instructions of what to build and the exact rendering and color palette. Or the exact packages you they can use as dependencies. But largely the world communicates together much better than the previous wave of outsourcing.
I would highly recommend not putting your home network at risk and poking holes into it. If you just self host a public site on your home network you should consider using cloudflare tunnel.
whats the risk with a static site genuine question? All I can think of is a CVE in html or nginx that seems pretty rare to me. If you're extra paranoid you can isolate the pi on your network.
imo it's not setting up the site once that's the problem, it's keeping it maintained indefinitely without making mistakes, because hostile automated systems will keep on rattling the doorknob like Jurassic Park velociraptors. (And I agree, for sophisticated users keeping it off your home network goes a long way towards preventing worst-case outcomes.)
No it just needs to have route to the internal IP of the docker host. And you expose your ports on that IP. Let me know if you need more details. You could also put the reverse proxy (Caddy in my case) on the docker host.
I see the value in that, but there are a few reasons that isn't on the immediate roadmap -- mainly, it shifts focus from measuring the model to measuring the harness. The agentic benchmark section you see on the site is comparable to how an agent would perform using an open harness like Pi. But latest tool-using models are pretty well adapted to any harness, so I think that's less of a factor in overall model performance.
I work with several local recyclers. Most of the machines they get are either usable but old, or just something somebody didn't want anymore! Truly damaged machines are rare.
On your website https://eh-trade.ca/ at the bottom it says "These opportunities are now closed, but they show the power of our momentum algorithm." and the total return is negative lol
