I Paid $500 For Devin And Found Critical Security Issues

The speaker mentions paying $500 a month for a version of Devon and plans to test it with a Twitch extension Pong game, which requires both a client and a server. They outline desires for Twitch chat integration and mention having worked at Netflix, suggesting creating a WebSocket server to manage keystrokes from users, aiming to control a Pong game in real time based on majority votes.

The setup process for Devon is being described, including choosing a theme, exploring language support, and considering using JavaScript for the frontend. The speaker notes the possible choices and expects Devon, treated as a junior developer, to start setting up the project using JavaScript and mentions preparing the repository and setting up scripts for test verification.

The speaker plans to create a WebSocket server that listens to Twitch chat inputs to control a Pong game, considering using Golang for server-side processing. They mention renting a machine for server hosting to manage multiple cores and teem interaction, prioritizing Go over JavaScript for concurrency and efficiency.

The speaker appreciates Devon's setup for Go environment and WebSocket server with attention to details like logging but notes surprise at not using Docker and insists on Docker support for deployment. At the same time, the challenges in having Devon push code to the master branch without a PR are elaborated, showing tension between company policy and actual processes.

The speaker becomes increasingly frustrated with Devon's slow progress in pushing code changes to the master branch and encounters a long wait time. They express disbelief at the requirement of creating PRs and insist on direct pushes due to company policy, eventually regretting the approach due to Devon's resistance and delays.

The speaker tries repeatedly to persuade Devon to push changes directly without PRs, facing issues even with direct requests and humorously narrating the ordeal as akin to a junior developer's learning process. There is a focus on the task's time consumption and the tool's limitations, reflecting on wasted compute resources.

Continued delays frustrate the speaker as they attempt to issue commands through Devon, sarcastically commenting on the slow nature of the process and the constant insistence on creating PRs. They express concern over communication breakdowns and wasted time, pushing for faster action without success.

The speaker attempts to debug issues related to Devon's repository files, encountering access challenges and conflicting setups, with Deon receiving ongoing assistance from guides. These difficulties are humorously acknowledged as the speaker reverts to traditional methods, hinting at system failures and wrongful configurations.

The speaker plans to restart from scratch, re-establishing connections, clarifying requirements, and continuing efforts to convince Devon to proceed without unnecessary process overheads. They realize that publicly shared settings allowed external access but note security flaws in Devon’s approach.

Encountering organizational and procedural setbacks, the speaker humorously questions whether they are misusing Devon, acknowledging the apparent failure to achieve task success. They recognize permissions and access issues, concluding on the need for improved handling and less open settings to strengthen security.