y2hhcmxlcw

Great, so now OpenAI has opened the door to pricing people out of AI access.

The o1-pro model in their charts is only ever so slightly better than the one I can get for $20 a month. To blur the lines of this they add in other features for $200 a month, but make no mistake, their best model is now 10x more expensive for 1% or so better results based on their charts.

What's next? The best models will soon cost $500 a month and only be available to enterprises? Seems they are opening the door to taking away public access to powerful models.

What about Attorneys and Doctors who have protected health information and client privileged information? Are they not to use Microsoft Products now?

What about any company with Trade Secret information? Are they also not to use Microsoft Products now?

I can truly relate to poor management. I'm unsure though if the author is referring at times to poor engineering/HR managers, or poor product managers. At my company they call the latter Product Owners but it's the same thing I believe. I deal so often with both being terrible. I've had terrible Engineering Managers, who simply don't understand the tech, and in the worst case they think they do but don't. Add in some office politics and they can make life truly unbearable. Same for Product Managers but it's a whole other array of chaos. I've had a tough time with poor managers, and so I can really relate to that aspect of this.

What I wonder though reading between the lines is if Gitlab has reached a point where they suffer from poor Product Managers/Product Owners. I see that in later stage startups and especially large orgs. One would hope Gitlab, by nature of its product space, would never suffer from that, so if they are that's disheartening. I'm unsure what at this point would really differentiate Gitlab from Github unless it's devex, and to have good devex they'd need engineering centric product vision, I hope Gitlab is not losing that by hiring an army of "Business Analysts" or MBA's. On the positive, in some respects I like hearing that HN comments drive the vision at Gitlab :)

I really relate to aspects of both of these comments above. 1. There is a last 1% problem, heck it's probably more like 10% problem with LLM generated code similar to the last mile problem with driverless cars. 2. The bigger thing that will impact the job market is, everyone, at global scale, is being told to learn to code. Every middle schooler in the US is seemingly assumed a failure by their school if they don't "learn to code". There will be so much exponential growth in junior devs over the coming years. Looking outside the US, software engineer salaries aren't that great. Can the US economy create an exponential number of high paying engineer jobs to offset the global exponential rise in qualified engineers trying to get those jobs? Companies will offshore via third parties like Accenture who will skim off the top the livable wage away from those people outside the US who Accenture offshores to, so even those people outside the US won't be winning. Any way you look at it, I believe there will be massive world wide pressure on US engineer jobs.

I can't agree more, totally opaque data will almost certainly be sent to an ever growing number of locations. If I so much as ask about it I'll be labelled a nutter.

Does this "criticism" or bullying or what not related to Androids exist among other age groups such as millennials? Or is it predominantly Gen Z?

I used this software to design my tiny house that I built with great success. It really helped me visualize the space. I didn't create an engineering ready floor plan with this so to speak. In other words, I intentionally left the measurements slightly relative which wouldn't work for most construction projects. In other words, if my bedroom ended up being 14ft by 10ft and 2 and 1/2 inches instead of 14x10' I was fine with that, it just meant other rooms slightly smaller. But give or take the width of dry wall and other factors it was worked fine. I found getting super precise measurements with this app difficult and so I didn't even try. I just let the guy building walls have a tad bit of freedom. Like I said, for most projects that would not work. Having said that, this app was a huge life savor and allowed me to really visualize the space and make key design decisions.

We believe this is the next generation of ads after the online advertising bubble pops. They can reach many people repetitively, although are unobtrusive on the horizon unlike billboards.

We want to facilitate the placement of logos on the surface of city streets, and give 90% of the advertising revenue back to the cities. This is an innovative new funding source that will generate substantial revenue for social issues and infrastructure needs, all without increasing taxes, fees, or debt.

> This is probably the most important task - Help the client to lead his project

For someone to do this, they would have to have client communication skills, at least somewhat thorough understanding of software development or the process, and an understanding of the client's business. I see this as a good thing. However, your example sounds to be a company that has external clients that you write software for. Do you not have account managers/principle types who interact with the clients, or is that more or less what a scrum master does there? Just curious, if you were an internal only dev shop that just develops software for stakeholders at your own company, would you see the role of a scrum master as significantly different?

Something I have wanted to ask the HN community, that this article brings up: what exactly does a scrum master do?

From what I have observed at one business, there is one scrum master on every team. Many of them know nothing about the business that business does, and have no technical background. I have seen developers spend sometimes an hour or more a day explaining to scrum masters what they just built, so that they can then go "communicate that up" to upper management or project management in opaque meetings developers aren't allowed to attend.

But what I can't figure out, is what they are actually supposed to do. At best, I see two points: 1. They do the traditional work of a project manager but on a team level, and communicate status up. 2. They are supposed to be some kind of "thought leader" on agile methodologies.

Can HN help shed some light on what this role should do? Perhaps my background has just been a bad experience in this regard. I suppose where I get stuck is, this seems to be the work that a dev lead used to do. Why make a full time job for a non-technical person to lead a technical team, below the management level?

I wonder at what point the financial pressure to stop designing bad software becomes so high that it overrides the political pressures that created the bad designs and practices? To a community like HN it's just normal every day thinking to design even at least a decent web application, but at some companies that's seen as either visionary and impossible or even immature. But at some point it seems there would be so much money on the line to trim the number of man hours going into maintenance nightmares they would fix it. I sometimes wonder if big companies will wake up to this across the country and there will be big lay offs becuase they adopt modern architecture and they don't need so many people? Does this seem feasible or will conways law hold even as financial pressure to do better starts to really go up? Or will the rewrites take even more people and therefore there won't be layoffs/pressure on job market?

At what point will corporations that still design massive systems as an unmaintanable monolith figure out they can architect things better and save a ton of developer dollars? At what point do they start taking good points from articles like this and either break those up into microservices or some other solution?