You’ve never met an average ASP.NET developer?
You’ve never met an average ASP.NET developer?
I suspect this is because of the looming end of Windows 10. There’s a large segment of Windows users, myself included, with Visual Studio being the only remaining tie to the Windows ecosystem. Extremely smart move by JetBrains, if true.
Welcome!
a good way to get yourself labeled by someone who thinks in memes.
What an effective way to put it.
Yeah, “lack of vision”, that’s definitely the problem.
The “vision” of the Israeli government has been clear for quite a while, now: Israeli ownership and settlement of the entire region, achieved by killing off or convincing to leave everyone that’s already there.
I appreciate the “carrot with a bit out of it” icon.
If you’re interested in detail, I can recommend this book: https://play.google.com/store/books/details?id=ncGVPtoZPHcC.
I mean, I’m paraphrasing, too.
Even better quote, I love using this one.
“So, with AI writing code for us, all we need is an unambiguous way to define, what all our business requirements are for the software, what all the edge cases are, and how it should handle them.”
“We in the industry call that ‘code.’”
I mean, REST-ful JSON APIs can be perfectly type-safe, if their developers actually take care to make them that way. And the self-descriptive nature of JSON is arguably a benefit in really large public-facing APIs. But yeah, gRPC forces a certain amount of type-safety and version control, and gRPC with protobuf is SUCH a pleasure to work with.
Give it time, though, it’s definitely gaining traction.
#4 for me.
Proper HTTP Status code for semantic identification. Duplicating that in the response body would be silly.
User-friendly “message” value for the lazy, who just wanna toss that up to the user. Also, ideally, this would be what a dev looks at in logs for troubelshooting.
Tightly-controlled unqiue identifier “code” for the error, allowing consumers to build their own contextual error handling or reporting on top of this system. Also, allows for more-detailed types of errors to be identified and given specific handling and recovery logic, beyond just the status code. Like, sure, there’s probably not gonna be multiple sub-types of 403 error, but there may be a bunch of different useful sub-types for a 400 on a form submission.
Anyone else this there’s actually nothing at all wrong with the “New” row of icons? Except for the triangle one, which is terrible in its “Original” version as well, as it indicates absolutely nothing about its app (I believe it’s Google Drive, right?). All the rest are clearly distinguishable, and have relevance to what the app does.
Case in point: Every single thing Microsoft is doing in Windows these days.
Inside the kernel, even!
My god, this speaks to me.
Don’t take this the wrong way, but this made me bust out laughing…
When you hold stock, don’t you need to sell it/liquidate it in order to make money?
Boy, if that isn’t just a perfect example of the perversion of our economic system. “You can’t make ACTUAL money with it, you can only make money by participating the meta gambling game.”
No, stock entitles you to dividends, which is just a fancy way of saying “a share of the profits”. Like, a company brings in A amount of money (gross income) in a year, spends B of that on payroll and whatnot (expenses), maybe puts away C of that into a savings or spending account, and everything that’s left, D, gets given to the owners. If you have stock in the company, that’s you.
Of course, dividends are generally very small (like, think savings interest) compared to what you can make trading and speculating, so it’s never good enough for the rich.
It’s also rather common for companies to pay no dividends, because they just put all the leftover money into C. Which isn’t even necessarily bad, it’s generally built on the idea that keeping the money in the company will give the company more room for growth, I.E. raising the stock price, with the assumption that that will be worth more than the dividends may have been. But for so many companies, that just never ends. Sooner or later, the growth won’t be sustainable, and many companies just collapse under their own weight, leaving the stock worthless.
The XZ exploit was found because some dude was investigating performance issues in a system, and noticed an unusual amount of time being spent in SSH processing, IIRC.
Windows 11 has ads NOW, in the enterprise install I’m provided at work.
For work, I have 2 monitors, and my docked laptop. The main two monitors are hugely beneficial for software development, as I can reference design docs or requirements while writing code, or I can have the debugger running on one screen, while the app runs on the other.
The laptop screen is where Teams and Outlook sit, so I can glance over at messages from the team, and maybe respond, without having to swap around any of my workspace.
This really reads to me like the perspective of a business major whose only concept of productivity is about what looks good on paper. He seems to think it’s a desirable goal for EVERY project to be completed with 0 latency. That’s absurd. If every single incoming requirement is a “top priority, this needs to go out as soon as possible” that’s a management failure. They either need to ACTUALLY prioritize requirements properly, or they need to bring in more people.
For the Chuck and Patty example, he describes Chuck finishing a task and sending it to Patty for review, and Patty not picking it up because she’s “busy.” Busy with what? If this task is the higher priority, why is she not switching to it as soon as it’s ready? Do either Chuck or Patty not know that this task is the current highest priority? Sounds like management failure. Is there not a system in place (whether automatic or not) for notifying people when high priority tasks are assigned? Also sounds like management failure. Is Patty just incapable of switching tasks within 30-60 minutes? She needs to work on her organization skills, or that management isn’t providing sufficient tooling for multitasking.
When a top-priority “this needs to go out ASAP” task is in play on my team, I’m either working on it, or I know it’s coming my way soon, and who it’s coming from, because my Project Lead has already coordinated that among all of us. Because that’s her job.
From the article…
Nonsense. If these are both top priorities, and the team has proper leadership, (and the 2 week estimate is actually accurate) 4 weeks is entirely achievable. If these are not top priorities, and the team has other work as well, then yeah, no shit it might be 6 weeks. You can’t just ignore the 2 weeks from Project C if it’s prioritized similarly to A and B. If A and B NEED to go out in 4 weeks, then prioritize them higher, and coordinate your team to make that happen.