Pretty interesting movement to be honest, but having more soybean internally would probably be better for them, silage is not a miracle, protein still has to come from somewhere, can't ferment whatever and expect it to fill soy's void.
Apart of the operational challenges mentioned in the article, of course, making it happen isn't trivial, it has costs as well.
They do get soy from Canada as well. Carney was diligent in making sure Canada has a new deal with China to maximize on that. It's one of the things Trump has blown up at him over, but Canada is also ridding itself of US reliance. US news doesn't seem to be covering the full story very often these days.
It's not the small number of Chinese electric cars Canada will be bringing in. It's Canada's replacing a big chunk of US soy in return that has him really irked. Much of the world is fed up and pushing USA away, while Trump continues to aim at the low hanging excuse-fruit instead of admitting (or recognizing?) his failure as a leader. It took starting an illegal war and complaining nobody would join him to distract his people from all his other problems. Less than half of USA still believes him. The entire rest of the world does not.
He keeps saying he doesn't need this and that from other countries, and then panicking when the other countries agree and move on.
Yeah, mine did, when chatgpt 3.5 came out I thought it was a fun incoherent toy and dedicated all of 10 minutes to it.
Last year I started using it as a copilot and in the second semester I started building AI/LLM based sales and marketing systems that now are most of my income.
I'm becoming one of those "and this is just the beggining for AI" enthusiasts :P
Ooh this sounds good, I feel the same problem but never imagined a solution, having a group chat sounds good, any chance this can be integrated in something like Antigravity?
"Time to kick off that new priority in your company!"
Web developer, mainly frontend and application logic, with basic infra and backend skills to get my work online.
Examples:
AI systems from scratch (no Langchain and similar), Interactive app screens, PDF generators, payment processing, maps and routes, VoIP, browser extensions, SFTP server client and more.
Stack: SvelteKit, Microsoft Azure functions, Netlify functions, AWS Lambda functions, Node, Docker, Appwrite as a full backend (Supabase alternative), Caddy as a front door (Nginx alternative).
Reach out to me vini.britox@gmail.com or just reply here.
There will always be someone whose job is to program computers to do things.
That's us, developers.
That will never change.
We're the ones dedicated to it.
Execs, managers, HR, salesmen, designers etc won't suddenly want to spend their whole days, not even half of their time, tinkering with a computer so it can do what they want.
Else Basic and Fortran would have made everyone software developers.
Exactly this. Sora 2.0 came out! It's amazing. I spent an evening with it and got bored. The amazing limitless potential of it blows my mind. But other than a couple of random attempt, thats simply not where my heart lies.
My Claude Code usage is through the roof, however.
This is exactly how I felt when Stable Diffusion came out in 2023. It turns out I am not an artist and eventually got bored by it whereas actual artists used it for hours, the same as we engineers use LLMs. The personality does not change, only the tool.
Yes, there will be always someone who is needed to program stuff. Totally agree with that.
But my question is "how many of those will be needed", because I am not saying that programmers are not needed.
When less numbers are needed, there will be so much competition in finding those jobs, esentially would also mean not able to find the work, as there will be always someone who would be willing to the job at lower wage and come to work with more youthful energy.
I've had a long career, and seen a number of systemic changes.
I've lived through two software "explosions" where minimal skills lead to large output. The first was web sites and the second was mobile.
Web sites are (even now) pretty easy. In the late 90's though, and early 2000's there was tremendous demand for web site creation. (Every business everywhere suddenly needed a web presence.) This lead to a massive surge in building-web-site training. No time for 3 year degree, barely time for 90 days of "click here, drag that".
So there was this huge percentage of "programmers" that had a very shallow skill set. When the bubble burst it was this group that bore the brunt.
Fast forward to 2007, and mobile apps become a "thing". Same pattern evolves, fast training, shallow understanding, apps do very little (most of the heavy lifting, if it exists at all, is on the backend.) Not a lot of time spent on UI or app flow etc.
This time around the work is also likely to be done offshore. Turns out simple skills can be taught anywhere, tiny programs can be built anywhere.
Worse, management typically didn't understand the importance of foundations like good database design, coherent code, forward thinking, maintainence etc. Programs are 10% creation, 90% maintainence (adding stuff, fixing stuff etc.) From a management point of view (and indeed from those swathes of shallow practioners) the only goal is "it works."
AI is this new (but really old) idea that shallowness is sufficient. And just like before it first replaces people who themselves have only shallow skills; who see "coding" as the goal of their job.
We are far from the end of this cycle, and who knows where it will go, but yes, those with shallow skills are likely to be first on the chopping block.
Those with better foundations (a better understanding of good and bad, perhaps with a deeper education, or deeper experience) and the ability to communicate that value to management are positioned well.
In other words, yes the demand for "lite" developers will implode. But at the same time demand for quality devs, who can tell good from bad (design, code, ui etc) goes up.
If you are a young graduate, you're going to be light on experience. If you're and older person, but had very shallow (or no) training you're easily replaced. If you think development is code, you're not gonna do well.
In truth development is not about code (and never has been). It's about all the processes that lead up to the code. Where possible (even at college level) try and focus on upskilling on "big picture" - understanding the needs of a business, the needs of the customer, the architecture and design that results in "good" or "bad".
AI is a tool. It's important to understand when it's doing good, but also when it's doing bad.
> AI is this new (but really old) idea that shallowness is sufficient.
That’s not the whole story and certainly not the core concern, which is more about developers who already have deep experience, using AI to multiply their output.
You've seen the "Dot-com" and "Mobile" cycles. This "AI cycle" feels faster, but the trap is the same: Mistaking Access for Mastery.
In Japanese martial arts, we have "Shuhari" (Obey, Digress, Separate).
AI gives everyone a shortcut to the final stage ("Look, I made an app!"), skipping the painful "Obey" stage where you learn why things break.
As you said, when the bubble bursts, only those who understand the "Foundation" (database design, consistency) will remain standing. The tools change, but the physics of complexity do not.
Apart of the operational challenges mentioned in the article, of course, making it happen isn't trivial, it has costs as well.
reply