Surprise! Absolutely Zero Ink in This Byte Stream [Gaming Tattoos Not Found]
Well, buckle up buttercups, because if you came here expecting the latest skin-deep sagas from the pixelated plains, you’re about to be as disappointed as finding out your raid dropped nothing but vendor trash. Turns out, the digital whispers we’ve intercepted are less about epic character portraits and more about… cloud computing kerfuffles. Who ordered that?
Instead of diving into the vibrant world of permanently etched controllers and lovingly rendered low-poly heroes, we’ve stumbled into a tech bro’s digital diary filled with complaints about cloud tokens and alleged corporate espionage. Prepare for a detour so wild, it makes a random encounter with a level 99 boss in the tutorial zone seem tame.
“you might be wondering why it’s putting out Jason here for this thing this is the phase two of the thing we’re building I’m waiting for cloud to give me my cloud Buck sus out kind of we want to build a chat interface that we can use later for it we got we’ve got the framework now down and it’s usable it talks to llm so it’s extensible so everyone can take it and do their own thing with it next is part two and for this a chatbot is too remedial but this can control a chat bot like that um the system for defining like experts and configuration settings shouldn’t be in the chat like that just takes too long and it keeps the uh it keeps the credentials in a bad place so you know my normal thing is to create a Micra service or service for this one would be a fullon service because I was playing out the front end with it um you know we talked about this you know I’ve already done last night with clud oh yeah one other thing I noticed is they added this now what’s this this is my laser focus a section on a additor I really keep feeling like whenever I’m doing projects all of a sudden they get like uh delayed like the other day when I was building something and then all of a sudden someone that one of these companies is like oh hey look what I”
-Staff BOSS
TL;DR
This isn’t about gaming tattoos, but rather a chaotic rant on cloud computing, AI interference, and frustrations with TypeScript. The speaker believes their ideas are being stolen by cloud services and AI developers, causing disruptions to their work. They’re adamant about using JavaScript with JSDocs over TypeScript and express frustration with people overriding their choices. They also discuss security concerns, past instances of idea theft, and a general distrust of big tech entities.
| Topic | Summary |
|---|---|
| Project Interference | The speaker suspects someone (possibly from Cloud or ChatGPT devs) is spying on their work, leading to crashes and disruptions. |
| JavaScript vs. TypeScript | Strong preference for JavaScript with JSDocs over TypeScript, arguing it prevents hallucinations in LLMs. |
| Frustration with Others | Annoyed that people assumed TypeScript was better for their project and changed it without consent. |
| Idea Theft Concerns | Claims past AI-related ideas were taken without proper compensation and fears the same will happen again. |
| Security & Privacy | Mentions implementing defensive measures against interference, worried about data leaks. |
| Internal Restructuring | Suggests companies are purging people who take credit for others’ work, hinting at industry shake-ups. |
If you were expecting tattoo news, you’re out of luck—this is just a tech-fueled rant with conspiracy vibes.
Our first “point” of… well, not exactly discussion, more like bewildered observation, centers around the speaker’s venture into building a chat interface. Now, you might think this has something to do with in-game communication or perhaps a chatbot that critiques your questionable gaming tattoos (we wish!), but alas, it’s purely about the backend. The real drama unfolds when the speaker suspects some shadowy figures are trying to peek at their digital blueprints.
“and then the reason that gets back to why I’m crashing right now this is what happens when they try to Jack into your conversation and stream a thought so they can see your ideas I guess it CRA their system’s not that good so I noticed it because it frequent like how often do you see this reason for a second and then it’s the Jason you know so so yeah he did you know it is a a little bit less concise here but looks like it broke their system and we cop them yeah so this is going to go up on a post like I’m trying to build something here for my students I don’t need someone with access to infinite tokens being like yeah I can build because like look at what happened with the last project I wanted I was very specific on my stack and I know whoever at Cloud was like no no no no no I know the perfect Frameworks and I’m like no you fucking idiot I picked JS with JS docs because it causes the llm less loopy like we saw last night when I started getting really annoyed I’m just like loo”
This brings us to our second non-topic: the speaker’s very strong opinions on coding languages and the audacity of others to suggest alternatives. The passion here is almost tattoo-worthy, if the topic wasn’t so far removed from, you know, actual tattoos. The speaker’s insistence on JavaScript with JS docs over TypeScript sounds less like a coding preference and more like a declaration of war against unsolicited advice. Imagine that level of conviction applied to arguing for a full back piece of a Snorlax eating ramen. We can only dream.
“k this is and then I went and JS docked everything I don’t know if he knows that uh that one committed was like Hey look at all this St and then it just started working really well but it still typescript so it’s still kind of it hallucinates too hard on typescript because there’s too much slop in its data set but not in JavaScript and I’d put in my original things I just want to do everything and that’s just some point he decided to take over in the middle of our Vite test and make everything in typescript and it’s like oh my God like I get it you guys thought you saw my project and you thought you could solve it better because you write L but this the problem with someone with three years of experience of coding is they think just because they solved a problem they solved it in the best way I’ve solved the problem like 10 12 times I wanted it in J JavaScript with JS docs for a very specific reason I was going to demonstrate how if you do that the lolm you get more work done even when the llms are you have to use a dumber model and it’s so and if you know and then there was also that story about uh the guy who wrote Ruby which is one of the best Frameworks I I actually don’t know Ruby I don’t like it at all but his I know it’s really good it was the original typescript by the way it was Ruby devs I hated them but I could not deny that it works um he even Switched Off typescript he’s like this is crap you know it’s just bloat on top of JavaScript with JS docs there’s like maybe a few generics whenever you need generics that’s about it but you can just kind of mimic it in JavaScript you can just kind of do it JavaScript and you can get around it and it’s like unless you’re writing a super generic heavy app that needs interfaces which is almost ever because 90% of the time there’s an interface and it’s used once and it’s just used it’s used as a JS stock like basically the reason it has the problem is you it uh typescript doesn’t have a separation layer between its documentation and its code it has documentation but it’s often bad whereas JavaScript with JS stock has a very clear uh whenever it’s put on the graph instead of it being a node and a sub a node just like one thing here’s the thing it becomes two thi”
Our final “insight” revolves around the speaker’s concerns about intellectual property and the fear of larger entities pilfering their brilliant ideas. While we’re usually concerned about artists getting ripped off for their incredible gaming tattoo designs, here the stakes are apparently multi-million dollar ideas about… something vaguely tech-related. The speaker’s anecdotes about past experiences with idea theft and the expectation of compensation are certainly dramatic, but still tragically devoid of any tattooed biceps.
“ngs here’s the JS stcs and here’s the code instead of it just being here’s the code so whenever it does the vector search through the thing there’s more space in the results for you get documentation in one vector search and you get uh you get you know and then that’s where all your type definitions are instead of it being in the code so you only get part of it and that’s why it hallucinates on types all the time because it it’ll just ignore interfaces to save space when it’s doing its little like compilation of your source for the LL you know breaking it down and stuff so if we had gone my way we probably would have been done early we would have been done before I spent that first like $50 right and then that’s the kind of shit man it’s like I I don’t know if they’re doing it on purpose or they’re just trying to like show off that they know little things but that the little things you guys know are dumb like I’m sitting here repeating through experience to this thing what we’re going to like we we don’t want to just create a single chain like we want to create multiple tool sets right that can be handed to multiple experts and the experts need something that can sit over their like group and double check their output so it’s not like the normal structures you would build which are just lists you need comp and this thing is fighting me and on top of that I don’t need the fucking chat GPT devs here to like come ruin it and you know not necessarily even out of spy just out of like let me show the best program in the world like you guys you guys saw all that shit during the clad stuff you know it’s like oh look there’s that idea he had from 3 months ago there’s that idea he said five month he says yes they were building it it’s fine um I better get like a $5 million or something $10 million but um yeah I don’t want to do that this time I’m trying to build like this product I don’t want y’all to come and be like we need to get more clicks on Twitter let’s go steal from Ari again you know and not pay him because all the stuff you guys took three years ago none of you paid for it ever except for like Ariel paid a few times and Logan paid a few times and back then the price was really cheap it was 100 bucks for ideas”
So, dear readers, if you were hoping for juicy gossip on that new Legend of Zelda sleeve or the latest Pokémon Go tattoo trends, you’ll have to keep searching. This particular batch of digital detritus offers zero in the way of skin art and a whole lot of tech industry angst.
Perhaps next time, the data streams will be kinder to our ink-loving hearts. Until then, may your own coding endeavors be less dramatic, and your tattoo inspirations more readily available.
Here are some key points from the transcript:
- Oh, the drama. It seems our intrepid speaker suspects a clandestine operation – a digital heist, if you will – perpetrated by the shadowy figures behind Cloud and ChatGPT. Apparently, these titans of tech, flush with their limitless “infinite tokens,” aren’t content with merely building their own empires; they’re trying to borrow our speaker’s brilliant ideas, siphoning them directly from the source – a process that, unsurprisingly, resulted in a spectacular system crash. One imagines the perpetrators chuckled as the speaker’s carefully crafted plans went down in flames (or, more accurately, in a cascade of error messages). The audacity! To not only invade their privacy but to potentially improve upon their work? The sheer nerve.
- Technical Choices (JavaScript with JSDocs vs. TypeScript): The speaker explicitly chose to use JavaScript with JSDocs for their project for a specific reason: they believe it causes the LLM less “loopy” behavior compared to TypeScript. They find TypeScript to “hallucinate too hard” due to “too much slop in its data set”. The speaker argues that JavaScript with JSDocs offers a clearer separation between code and documentation during vector search, leading to better results and fewer type hallucinations. They had initially planned to demonstrate how this approach could be more efficient even with “dumber models”.
- Frustration with Others’ Assumptions: The speaker is annoyed by individuals (specifically mentioning someone at Cloud) who attempted to convert their project to TypeScript during a Vite test, assuming they could solve it better because they write LLMs. The speaker, with more experience solving this type of problem, had a deliberate reason for choosing JavaScript and felt their expertise was disregarded.
- Concerns about Idea Theft and Lack of Compensation: The speaker references past instances where they shared ideas with AI companies (specifically mentioning Cloud and the ChatGPT developers) and expresses dissatisfaction with the lack of proper compensation, except for a few individuals like Ariel and Logan who paid a small amount for ideas in the past. They are worried about their current project being similarly exploited for clicks or product development without recognition or payment.
- Security and Privacy Concerns: The speaker alludes to security concerns and potential retaliation if their work is interfered with again. They mention defense systems and other measures in place. They also mention a past situation involving leaks and negotiations.
- Internal Restructuring: Towards the end of the transcript, the speaker touches on the topic of internal restructuring within some organizations, where those taking credit for others’ work might be let go, while hardworking individuals may still have opportunities.