Development Skills that are future proof

Barbarian Conan said:
.Net Framework is dead. .Net Core lives as .Net 5.

They just kept them separate while the whole of the .Net framework was migrated to .Net Core.

It used to be .Net Framework 4 and .Net Core 3.
Now it's just .Net 5.

In fact:
View attachment 1170936
Click to expand...
Exactly... .Net core was an intermediate project to e.g.
  • proof the concept
  • and/or serve as a placeholder for their long term ambition to create a cross platform .Net Framework.
As with any merger of temporary / intermediate projects; their terminology will inevitably be phased out.
 
Hamster said:
Clueless middle management is future proof. Even in a fully remote work world you'll never get rid of those oxygen thieves.
Click to expand...

Jeez dude. Seems that you're not having a good day. I'll go ahead and schedule a 2 hour 1-on-1 with you and we'll make some pointers to bring up in the retro at the end of the sprint. Just remember, don't raise any points about the process or the documentation requirements as those are set in stone due to some arb rule from 5 years ago. Also, we're adding in some additional approval steps, the business manager now wants sight of your code submits to ensure it's pythonic in nature, I explained that we're using Javascript, but he says it should be the same, so make sure your comments are super clear in their explanation.
 
Last edited:
GhostSixFour said:
Jeez dude. Seems that you're not having a good day. I'll go ahead and schedule a 1-on-1 with you and we'll make some pointers to bring up in the retro at the end of the sprint. Just remember, don't raise any points about the process or the documentation requirements as those are set in stone due to some arb rule from 5 years ago. Also, we're adding in some additional approval steps, the business manager now wants sight of your code submits to ensure it's pythonic in nature, I explained that we're using Javascript, but he says it should be the same, so make sure your comments are super clear in their explanation.
Click to expand...
Also we have a new policy that all developers need to submit a report detailing the number of lines of code typed on a daily basis. And please stop asking about your stapler!!
 
Russell S said:
Also we have a new policy that all developers need to submit a report detailing the number of lines of code typed on a daily basis. And please stop asking about your stapler!!
Click to expand...

This gives me an idea for a new dashboard, hours googled vs lines submitted. I'll speak to the higher ups and get this authorised for you guys, what a wonderful suggestion, thank you Russell for being a team player and your fantastic outside the box thinking.
 
GhostSixFour said:
This gives me an idea for a new dashboard, hours googled vs lines submitted. I'll speak to the higher ups and get this authorised for you guys, what a wonderful suggestion, thank you Russell for being a team player and your fantastic outside the box thinking.
Click to expand...
Extra bonus for negative submissions i.e. reductive??
 
Hamster said:
/quits
Click to expand...

Dont quit I have some AI that will take short concise code and quadruple the code lines and add some incoherent comments to make box checkers happy.
 
Russell S said:
Also we have a new policy that all developers need to submit a report detailing the number of lines of code typed on a daily basis. And please stop asking about your stapler!!
Click to expand...

LoC is such an idiotic metric, but I would rather STFU and do it before they get the idea to do Function Point Counting instead.

Function point counting is a measurement concept that was originated in 1979 by Allan Albrecht of IBM. As part of this concept, Albrecht determined software could be sized by assessing processed external transactions. IBM advanced this methodology in 1984 to include the evaluation of application complexity and categorization of system characteristics. Today, the function point counting methodology has been refined to provide a dependable, repeatable form of code analysis through automated analysis solutions.

Function point counting is unique because it allows organizations to evaluate the functional weight of software deliverables during any point of the development life cycle without necessarily understanding the functionality itself. The takes into account these factors during calculation:

  • External Inputs
  • External Outputs
  • Internal Logical Files
  • External Interfaces
Function point counting calculates a single value, which represents the total amount of functionality being delivered by an application. Size is then communicated as a stand-alone value or segmented to display information regarding specific software components.
Click to expand...

**** everything about FPC, but go in extra hard and extra dry on the tools to "help" you do it.
 
GhostSixFour said:
Why should you be incentivised to be better? It should form part of your development plan..
Click to expand...
That's the irony isn't it; and what I was trying to illustrate.

For example:
If you structure incentives on lines submitted; you're going to get a lot of garbage / unnecessary code; plus not all lines are equal, as some submissions could make matters much worse; whereas some reductive submissions could vastly improve the outcome.
 
jbrunevader said:
That's the irony isn't it; and what I was trying to illustrate.

For example:
If you structure incentives on lines submitted; you're going to get a lot of garbage / unnecessary code; plus not all lines are equal, as some submissions could make matters much worse; whereas some reductive submissions could vastly improve the outcome.
Click to expand...

Or the classic where teams get measure on story points delivered and suddenly a simple header change becomes an 8..... :)
 
Do some people really work in places with these types of random metrics?
 
_kabal_ said:
Do some people really work in places with these types of random metrics?
Click to expand...

Half my time project managing/scrum mastering projects is spent fighting this type of idiocy.
I loathe giving business access to dashboards cause sure as **** within a week they'll be asking for this or that and wanting to use it as useless metrics so they can all stand in a circle giving each other a reach around, and sing about they can track the project and how it will all be done on time.
 
Russell S said:
Also we have a new policy that all developers need to submit a report detailing the number of lines of code typed on a daily basis. And please stop asking about your stapler!!
Click to expand...
Wow what a kark employer/company... bean counters fully in control.
They make us do timesheets... and they don't even check 'cause I tested them one month, they had no idea I didn't submit a timesheet at all..
 
Russell S said:
Also we have a new policy that all developers need to submit a report detailing the number of lines of code typed on a daily basis. And please stop asking about your stapler!!
Click to expand...

That's just wrong


I mean I can do in 5 lines what others might do in 50

Which one is better?

Ie, that's a useless metric.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X