Country-specific local job boards are best. Big tech companies (LinkedIn, Indeed, Glassdoor) are terrible for this purpose. Always apply directly on a potential employers' website, best through email if they accept that. Even printing your application and sending it by mail is a far better option than applying through LinkedIn or Indeed.
It's still used for job hunting and recruiting unfortunately. I got a real message from a real recruiter for a 5k+ employee software company on it just last week. My friends and colleagues dealing with layoffs have had to update their profiles. :(
Sadly, LinkedIn has replaced email for initial contact after fairs or in-person client meetings. New real-world contacts look you up on LinkedIn and then use it to ask for things like your email address or mobile number. Because of this, I'm even verified :-(.
Even though I use LinkedIn basically the same way Internet Explorer was used in 2009 (purely as a Firefox or Chrome downloader but not for browsing). LinkedIn is my initial contact details exchange, but not the platform to communicate.
> Isn't that just all ai slop?
It is. I basically get zero useful input. Just biased, shallow rubbish. If there is valuable content it is usually cross-posted from authors who also run blogs I already follow.
The website has an about page that explains some of the reasons why this project exists. The first heading in the readme of their repo is "Vision". The creators of this project are people with a track record of creating popular, high quality, useful Javascript projects.
I'd say the probability that some thought has gone into this project it pretty high. Your reply stating that this was created without any though or effort is, ironically the least thoughtful, laziest and least useful response possible.
The prolific inventor’s dilemma. But to be fair developers have been making whatever they want since the beginning. Sometimes there doesn’t have to be a ‘why?’.
Haha this. I understand the appeal of "but I can probably roll my own" and "Oh that's a good idea, let's jump into coding" but pre-vibe bots, the effort required would make folks stop and think before jumping into it - is it really a good idea? should I do it just because I can? what problem is it really solving? Who will use this? etc.
Code isn't assembly, code is required to sufficiently express English in a way that is unambiguous.
You can't translate plain English into unambiguous code. Period. Not even engineers can. The only way this translation happens is that humans are good enough at communicating to get to a point that code can be produced and iterated on to produce an outcome with enough context the thing doesn't fall over after a week.
The only thing stopping AI doing this is the right communication models and enough context.
As an engineer by trade. Im quickly realizing how fucked we are right now.
I give us maybe 2-3 years until the last engineering roles are posted. Maybe longer depending on how many businesses survive the crash while refusing to automate their workflows.
Most of us are going to start transferring skills to more of a prompt programming and coordinator role.
>Most of us are going to start transferring skills to more of a prompt programming and coordinator role.
Human code reviews and in-depth understanding of architecture remain important even for codebases with comprehensive test suites because treating a computer program solely as a black box does not allow one to reason precisely about the program when it encounters general inputs. Relying solely on black box testing simply offloads more QA to production users.
In a future world where humans rely entirely on machines to interpret their ambiguous instructions, who does the checking and what do the checks involve?
Im still of the opinion that programming should be enjoyed more as a hobby/skill now. Just like a builder cannot build an entire house by himself, programmers now cannot build without an orchestrator.
Nonetheless, you can build a cabiner just for funsies and to feel like you've accomplished something
reply