|
Richard Andrew x64 wrote: This, combined with no-code platforms, will usher in the age of the average Joe being able to try to develop software.
FTFY
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
It's about small teams, microservices, bias towards serverless, and having the creator of Java on standby I'm guessing in The Cloud(tm)?
|
|
|
|
|
Quote: A team is typically 6-15 people, Lee and Zhadanovsky said, also known as "two pizza teams,"
The fact that Amazon considers as few as 1-2 slices of pizza (15 person team, 8 to 16 cut pizzas) as adequate says a lot about how they nickle and dime themselves internally as well as how little they care about individual employees preferences: 2 pizzas means you're limited to the most common default options and ![Elephant | [mastadon]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/elephant.gif) anyone who doesn't care for them. 6 people would generally be 3 or 4 medium/large pizzas most places I work just to give enough for a full meal and options beyond plain cheese and pepperoni.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
|
|
|
|
|
I was wondering if anyone would point that out. IMO a 1-2 pizza team is me. 
TTFN - Kent
|
|
|
|
|
Visual Studio is a rich IDE that provides an abundant collection of tools and functionality for developers to use in every stage of software development. If it's broke, they won't fix it
Bad news for that Workflow Foundation fan?
|
|
|
|
|
Hopefully this will become a standard for all development environments. Forcing developers to swap out unsupported components will lead to fewer breaches like the Equifax and Experian breaches.
|
|
|
|
|
Alternatively, if the removal is forced, it will result in more developers sticking with out-of-date IDEs simply so they don't have to work out how to update working code to the latest-and-greatest framework, and then coordinate updating multiple servers to that framework, before being able to deploy even the smallest tweak to their application.
Eg: If MS decided that ASP.NET WebForms is no longer supported, and forcibly removed it from Visual Studio, that would break our existing ASP.NET MVC5 apps which need to display and/or export SQL Server Reporting Services reports. Rather than writing our own replacement for the ReportViewer control using a 3rd-party SSRS library, or following MS's "solution" of paying for PowerBI Premium licenses, we'd have to stick with an outdated version of Visual Studio.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Richard Deeming wrote: we'd have to stick with an outdated version of Visual Studio.
In the automation world has been like that for a long time.
That's why I started to use VMs a lot, to keep different constellations of development software that were not compatible to each other.
First contact to a new customer...
- Do you have already a running system in your maintenance department? Yes? Please send me a screenshot of the installed software versioning list (automated functionality).
- Do we already have a VM with that basic constellation? No? Add two days to create one in the cost estimation.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Richard Deeming wrote: Eg: If MS decided that ASP.NET WebForms is no longer supported, and forcibly removed it from Visual Studio, that would break our existing ASP.NET MVC5 apps which need to display and/or export SQL Server Reporting Services reports. Rather than writing our own replacement for the ReportViewer control using a 3rd-party SSRS library, or following MS's "solution" of paying for PowerBI Premium licenses, we'd have to stick with an outdated version of Visual Studio.
What you seem to have missed is that corporate IT forcing it down your throat is also a feature; so when MS deprecates something major your choices will either be spending half a year doing a rewrite (obviously not on corporate ITs budget 🙄) or having to tell your boss that in fact it's impossible to fix a typo on your apps main screen. 🤦🏽♂️
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
|
|
|
|
|
A clear win for setting workplace boundaries – but a sad loss for happy hours the world over. Woo and/or Hoo
You gotta fight
for your right
to not paaaaaarrrrrrtay!
|
|
|
|
|
Quote: The man, referred to as Mr T.
I pity the fool!
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
The good news is that your employer can't force you to party.
The bad news is that this only applies to employees in France.
Could we get a ruling from the UN Commission on Human Rights? 
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
In most of the EU the employer can force very little onto the employees and it's (more or less) strictly defined by the contract and relevant legislation. Unless you're a promoter or PR, partying is never mandatory during work hours.
Outside of work hours, the employer has literally no power whatsoever.
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Researchers at Paderborn University in Germany have built a robot that can knock a ball into a hole using a club on a putting green on most attempts. Because the only thing that would make golfing more exciting is to have an AI play it
Wait... did I say "exciting"? I meant the opposite of that.
|
|
|
|
|
Well if we're going to have Robot Overlords, they should be able to play the sport of CEOs.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated.
|
|
|
|
|
Over 5.4 million Twitter user records containing non-public information stolen using an API vulnerability fixed in January have been shared for free on a hacker forum. I'm sure they'll get right to fixing that
Yes, this all happened before the purchase.
|
|
|
|
|
Don't worry. Musk has vouched that they were all bots.
|
|
|
|
|
I am of the opinion that Twitter execs desperately wanted to be bought by Musk and did a massive rug pull.
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
I came to the same conclusion last week when this hit the news.
|
|
|
|
|
I should first clarify that I would never come out against the idea of writing tests for your code. An abbreviated list
Ignoring the horror of the title, of course.
|
|
|
|
|
This article makes the common mistake that tests are Unit Test, or tests of small pieces of code.
With Test First, the first tests you write should be at the Specification or Requirements level.
Tools such as SpecFlow and Cucumber are great ways to do this.
Then, as you start to start creating things to implement the requirements, you add tests for the sub-requirements being implemented. Then write just enough code to make the tests work. I have found that I write around half the code, and complete projects in 1/3 to 1/2 the time as colleagues who just start coding. Writing high level tests forces you to get a better understanding of what you are going to implement without getting sidetracked by coding and implementation details.
Also, if requirements change, you change the relevant tests, and fix the ones that no longer pass.
In many cases, you don't need to test the low-level methods and classes if the higher-level requirements/tests cover the full functionality, error-handling, and edge cases.
In reality, who cares how the code is implemented if it meets the requirements. In fact, by not testing the actual methods, it much easier to refactor and re-architect a code base.
Remember, job is not to write code, but to implement required functionality and quality, as defined by the project/customer/contract.
"Time flies like an arrow. Fruit flies like a banana."
|
|
|
|
|
We hear that many of you would like to see more details of the improvements which the MSVC backend team have been working on recently. "She gotta pack much back"
|
|
|
|
|
The release of the enterprise version of the encrypted messaging service, announced at AWS re:Invent, is designed to allow secure collaboration across messaging, voice, video and file sharing. People that sent this message also sent these messages
Too obtuse?
|
|
|
|
|
Analyzers did become an integral part of the .NET ecosystem. Their main responsibility is to find potential code issues and warn you And how did that bug make you feel?
|
|
|
|
|
Probably the most frustrating thing that happens to me as a developer is getting stuck. Get some friends to push?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
