I've recently finished a browser game specifically targeting an old iPad Air 1 we had lying around the house.
I had a working version after a weekend, but it took me a month to make it run smoothly on an over 10 years old mobile device. And the most recent browser available is almost 10 years old.
Surprisingly I didn't missed too many "modern" JS features, as these were mostly functional programming oriented which doesn't play well with optimization anyways, and the ES6 was more than enough as a programming platform.
Anyway, what I'm trying to say is that "the best practice" should be making your apps fast and accessible - as much as you can without having to sacrifice something you value - instead of chasing the latest and shiniest.
Gemini web? Probably simonw's strat from the top comment.
There's a plugin for Antigravity that's listed on initial setup (yay bundleware! :) but... yeah if you're using consumer gemini, i'd switch to the Tasks mode because it's more agentic nature helps.
In fact I just did this and it works. :p It regular Gemini, it said it did but kinda liked :) So there it'd be
I started my whole programming career as a freelancer and worked fully remotely for 6 years before ever going to an office. But that's a bit different, because I advertised as a freelancer/consultant, and in that period I rarely worked in a team. And even when I worked in a team, my areas of responsibility were completely mine.
On one hand I vividly recall my last BigCo full time employment. I enrolled to a newly opened office, which at that point in time wasn't even an office but a few rented cubicles in WeWork-like space. My daily routine for first couple of months was to come to the office, get into my cubicle and login to the Skype call with the rest of the people I was working - in different offices.
And for the rest of the day I sat there alone, occasionally hoping on other impromptu Skype calls.
I specifically asked couple of times if it would be possible for me to work from home, because I have zero personal interactions in the office, but over and over again I was told that WFH is strictly forbidden by the company policy.
That was pre-covid.
On the other hand, as someone who wore hats of leader/manager/director I have to admit - to this day - I find building teams, from ground up, in remote environment, almost impossible.
My very first office job had a very clever trick up their sleeve - we had a free lunch each day. Nobody skips a free lunch. Took me some time to realize how clever it was. To this day I have a draft of article in my desk titled "eat your scrum master".
Oh, and 20 years ago everyone was smoking. Between smoking, lunch, and bumping into each other at coffee desk - everyone knew everything. It's so simple - people like to talk, but eventually you'll run of small talk topics and start talking about the job.
> My very first office job had a very clever trick up their sleeve - we had a free lunch each day. Nobody skips a free lunch
I was recently diagnosed with celiac, so I'm pretty iffy around restaurant food in general
But even before I was diagnosed, I would much rather choose what I want for lunch than have whatever the office decided to buy.
Then again I've never really done well in office jobs, my career really never went anywhere until I started working remote and could stop trying to figure out the office politics bullshit
It's not specifically against you, but whenever I bring up this memory everyone's first reaction is just that - I won't be told what I can eat, fuck off.
But this arrangement doesn't mean you only have one option. Most of the time you have a few. Sometimes - as was in my case mentioned in the post - you could specifically say what you want. And you could want anything you'd like, as long as it could be delivered. This wasn't Google, so we didn't had chef, but we had options.
The only time I saw the company took the decision was when I had my stint at CDPR, when they advertised free lunch. The part they didn't advertised was the part the lunch was arriving at 6pm. But still they were ordering for 2-3 different restaurants.
> whenever I bring up this memory everyone's first reaction is just that - I won't be told what I can eat, fuck off
I think you took this quite a bit harsher than I was intending so sorry about that
But yeah, I think this is maybe a cultural or generational difference or something. I'm almost 40 now but I've never really been interested in work lunch stuff. For me, Lunch break is a break from work and coworkers and expectations not just a time to eat food. It's definitely not a time for team building activities, schedule those during working hours thanks.
I swear I heard this exact story some 2-3 weeks ago.
If I recall that story correctly, a dev noticed that after asking Claude to test an API it started injecting his email into the test data. Without asking.
But what was the weirdest part of that story - Claude never saw that email. Dev claimed that the email Claude was using was his business email, and it wasn't even present on his developer machine anywhere.
You did. This issue has come up every few weeks for months. On 25th October Boris Cherney was tagged multiple times in a discussion on Threads where he’s regularly active.
I can see why this could be interesting for non-tech people, but c'mon, it's just words added to your context, not something magical. I've seen massive hype over Pockock's skills and took a deep dive into them just to find out it's basically "don't make mistakes" on steroids.
I mean, input tokens are cheap, and people would be so much better with just using speech-to-text instead of all of this crap.
The goal is re-usability and (somewhat) reproducibility. Why would I want to repeat the same input tokens from scratch every time I need to redo the same process? You can store the prompt in your notes, a text file on your desktop, or ... in a skill.
Though I agree that it's often rather overhyped for what it is and flows like the one here would likely need additional fine-tuning to match the user / company needs.
I've recently finished a browser game specifically targeting an old iPad Air 1 we had lying around the house.
I had a working version after a weekend, but it took me a month to make it run smoothly on an over 10 years old mobile device. And the most recent browser available is almost 10 years old.
Surprisingly I didn't missed too many "modern" JS features, as these were mostly functional programming oriented which doesn't play well with optimization anyways, and the ES6 was more than enough as a programming platform.
Anyway, what I'm trying to say is that "the best practice" should be making your apps fast and accessible - as much as you can without having to sacrifice something you value - instead of chasing the latest and shiniest.
Don't be a fashion driven developer. :)
reply