As someone who is still on 12 pro and probably won't upgrade to a 17 because of no real need - there really is no better way to ensure my repeat business than selling me a phone that lasted me this long.
I think, generally speaking there are a lot of contexts here clashing of what people mean by "feature" and "product". For some, "the product" might be a 30+ year legacy multi million loc codebase getting slowly improved, but still old and inadequate and probably full of technical debt and a lot of domain knowledge needed to navigate.
For others "the product" will be a website with a few 10k loc behind the scenes.
Getting a feature out in those two environments is not the same thing.
Yeah, I'm really wondering if I'm dumb or something with this whole AI train, but my job as a developer that maintains existing (sometimes quite old) systems is much more about determining what actually needs to be done, gathering lost / not lost knowledge about the existing state of things in systems and figuring out where to change the code for maximum impact and minimal side effects. Lots of talking to customers/non-technical people as well to figure out if existing features can cover something they need and they just don't know about it and I happen to know about it etc.
I've been watching the AI hype (again) and it's completely going over my head, I really really don't get it - I doubt {x}GPT would be able to analyze hundreds of thousands of project code across a big system (multiple languages, multiple services, interconnectedness of everything) and tell me what to do, even in the case I would want to paste in everything proprietary to a 3rd party service which I really don't.
Maybe it just works for a subset of programming, but then again I don't really see how it differs to reading docs for generating boilerplate or whatever it's useful for in greenfield projects. I was also not really impressed by it generating improvements to code when you ask it the right questions since that's the hard part of the job, not typing out the code.
Don't downplay yourself like that. A 25k token GPT model is a step in that direction but we're 3 - 15 years from your vision of valuable.
Currently, the Language Models (GPT or GithubCopilot) are mostly good as ... copilots. You bounce off ideas off them or use them to kickstart something you want to do. It's great for junior devs (me!) but it still cannot do big context or cognition (what you describe), that part will be done by humans for quite a while.
While 500kcal is a good meal (by no means large), it's also less than a 100 gram chocolate bar which I can devour in about 25 seconds. Most of the problem nowadays it that a lot of food is of EXTREME caloric density.
Yeah and the guy literally says nothing about his diet.
I've been going to the gym for 2 years now with a personal trainer - mostly a wholesome approach and even when doing HIIT intervals, I'm not getting even close to my max of 194 I've seen before starting going to the gym when I tried to climb the tiny hill close to my house on my bike.
His experience seems anecdotal at best and an extreme case of cherry picking alongside that. I do feel some nausea after a decent workout usually and it does suppress my appetite for a few hours, but I know of people that are just ravenous after working out.
> I'm not getting even close to my max of 194 I've seen before starting going to the gym when I tried to climb the tiny hill close to my house on my bike.
Are you sure that you are climbing fast enough? Gym training isn't necessarily the best way to prepare for cycling.
Gym for sure is not the best way, but I'm not really lifting heavy weights, it's more of a work on calisthenics, some cardio (usually rowing) and some mobility exercises with the occasional compound lift here and there, cycling is just my preferred cardio for multiple reasons - I can actually travel moderate distances as opposed to running, it's lower impact and I find it much more relaxing than running for instance.
Also, I'm not sure if you understood correctly - I've hit my 194 when I was out of shape and stepped on my bike and tried to climb the tiny hill (after doing about 20km or so). After about 200m of distance with about a 6% gradient, my HR was 194 and I had to step off the bike, my lungs felt like they were extending from my groin all the way to my upper arms on boths sides :D.
After going to the gym for two years I've never seen more than 187 during the HIIT sessions that we had (usually it's something along the lines 20 calories max effort rowing with 15-30 seconds rest, anywhere from 6-10 series) so my experience directly contradicts what has happened to him.
It's an alternative, but in windows minimizing works on a window, not the entire app. The philosophies of [apps] vs [windows] are just too different, I don't think anyone that wants windows can be happy out-of-the-box, with the apps vs windows thing plus with the minimizing being basically "putting the app to sleep" on macOS vs "putting the app away" on windows.
I would just like to add that this thread is an absolute gold mine of information. I haven't been full time on a mac since the corona-induced WFH where I just picked stuff up on my desktop, but recently I've picked up an M1 Air to work on and separate "home" from "work" and a lot of the suggestions here provide incredible insight into slight annoyances that I find within Mac OS. Not that I care that much since like 99% of my time is spent in tmux and I try to avoid the touchpad/mouse like the plague as much as possible, but it's nice to read the insight people provide here.
maybe that's the price they're willing to pay for whatever benefits they get from remote work, and maybe they're missing out on what they consider bad things more than good, everyone is different.
An issue is remote people may be at a disadvantage because they are remote and therefore may suffer consequences of not being in the office (visibility, chit chat, camaraderie, etc.) but they (we, or some portion) may feel they are unfairly suffering from unequal opportunity. On the other hand, they/we specifically have made the choice to be remote despite the inherent disadvantages (and also advantages though in another dimension).
Agreed, as I said, some people will not consider things like visibility, chit chat, camaraderie valuable. I don't really want to be friends with people I work with, or generally spend time with my coworkers when I'm in the office since I already spend 8+ hours daily looking at them. Even when remote, people I work with are not my friends, those are a separate bunch of people, I'm there to do my job, solve problems and I don't need camaraderie, chit chat or visibility for that. On the other hand, relying too much on office chit chat tends to make knowledge more word-of-mouth than written down if there are no documentation practices in place, while its practically a necessity to write things down when you're working remotely and that's a huge gain in my book. I think it's really really hard to to decisively say that one model is better than the other, but it does smell like distrust and micromanagement from the higher-ups to me when office work is considered mandatory.
