|
Kent Sharkey wrote: Moving the dev team on to something else? Fixing bugs, I hope?
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.
|
|
|
|
|
No, they found out that the devs working on sql extensions were quite adept at making new icons and round corners on boxes that were round back in 2001.
I reckon this would be like NASA finding people that can re-learn how to build a Saturn 5 rocket, or lunar lander.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
If you're worried about privacy, it might be time to cover up your front door's peephole. Beware of Peeping Toms with lasers
As well as single-photon avalanche photodetectors, and a lot of computing power. Or just anyone from Stanford.
|
|
|
|
|
Most people already have alexa, echo, siri or things like that... no big concerns about privacy.
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.
|
|
|
|
|
Exactly why I don't have any of the above.
Now I've got to worry about blocking keyholes and windows against lasers ...
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Visual Studio 2022 seeks to greatly improve your overall development experience, and we’re moving forward with that journey in improving VS extension writing and usage today! I'll tip my hat to the new extension model...
Caution: Article contains a high volume of exclamation marks!
|
|
|
|
|
Is it only me? Or did someone from marketing take over the management of VS Team?
I fear they are trying to make it soooo cool and extensible, that will end breaking one of the few really, really good products they have.
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.
|
|
|
|
|
A look at all the different ways to build for desktop today. Choose your life partner wisely. A roadmap for the lost
Either before, or after. Your choice.
|
|
|
|
|
And then there are things that actually work: Win32 API, MFC, Qt, Tk, GTK, ...
|
|
|
|
|
When it comes to remote work, security is often the last thing on the priority list. The other 9% were doing it anyway
|
|
|
|
|
When it comes to remote work? Hah...
Security has been dropped down to the bottom of the list in most business, no matter in which aspect.
First when a company gets hit (and I mean hit hard) there is maybe a change of mind.
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.
|
|
|
|
|
Researchers describe how they applied rheology to the seemingly quaint purpose of improving the quality of a cup of black tea. Because not everything is solved via coffee
Sometimes you just need a cuppa
|
|
|
|
|
Kent Sharkey wrote: Because not everything is solved via coffee Of course not... we do have bacon too
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.
|
|
|
|
|
Google on Wednesday ramped up cloud collaboration tools for businesses, expecting "hybrid" work routines to remain even after the pandemic has ended. So we'll be powered by both electricity and gas?
The addition of electricity to my office will definitely help the ... ambiance.
|
|
|
|
|
Visual Studio Code is now using machine learning to detect what programming language is being used in a pasted-in file and then automatically set the appropriate mode. Good luck with this one: for(i=0;i
|
|
|
|
|
I suppose they have been inspired by the paste assistant in CP
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.
|
|
|
|
|
LG says it’s developed a new material that can create displays with “a surface as hard as glass and folding parts as flexible as plastic.” Is that a folding phone in your pocket, or do you just have too much disposable income?
I guess that's more of an "and" question.
|
|
|
|
|
If I wanted such a big display I would buy a tablet...
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.
|
|
|
|
|
Technical debt impacts the whole company, but it especially affects engineers as more tech debt means more bugs, performance issues, downtime, slow delivery, lack of predictability in sprints, and therefore less time to work on new exciting projects. Declare technical bankruptcy?
|
|
|
|
|
I love technical debt. No employees want to work on "old stuff". Meanwhile, I'm paying off my mortgage.
Technical debt is a buzzword that I believe has no real meaning.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
charlieg wrote: Technical debt is a buzzword that I believe has no real meaning.
I think you're correct.
It seems to me that what people increasingly call "technical debt" is just... code. The stuff you wrote yesterday. You know, the stuff that actually sells licences, seats, whatever.
There is far too great a trend to declare everything over a certain (ever-shortening) age as "legacy" and pretend that one should just start again from scratch. No. This is a lazy and, frankly, incompetent approach. Sure, I accept there does come a point when starting afresh makes sense but it should never be a common choice. The cries of "legacy" are becoming too common to be realistic or sane.
Coding is about maintenance, not just the new and shiny.
Yes, I know that the spotlight and fame tends to get focussed on the new and shiny, i.e. on the re-invention of problems already solved with "legacy" code, and on those who work on the new and shiny, but this does not make maintenance any less important, any less necessary, or any less valid.
Everyone wants to be a new and shiny superstar. This is understandable perhaps. But it doesn't mean that wasting money on starting afresh every year or whatever is justified, sane or sensible.
|
|
|
|
|
For us, technical debt is code that (appears to) works fine, but that everyone recognizes could use a rethink/re-implementation without changing the result. We have a number of things that are technical debt. Some are (much) more involved than others, and most of them are in the back-end. The two most annoying to me are:
0) For instance, we have a table that has over 600 columns, and that requires a crapload of dynamic sql to access. This could easily be stored in an unpivoted fashion and eliminate the dynamic sql altogether, yes still provide the same data that was expected.
1) Another technical debt item is our javascript. Instead of using a single function to create a grid that accepts an "options" parameter, we have about 30 different functions that create their own grids, each in a wildly imaginative way. We could significantly reduce the code footprint if we used one grid function to rule them all.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
#realJSOP wrote: We could significantly reduce the code footprint if we used one grid function to rule them all.
Obligatory XKCD[^].
Between devs who don't know that it exists, and devs who need an option that it doesn't support but are afraid to modify it, 18 months after creating the OGFTRTA function you'll be back to at least 31 grid functions.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
If code that uses the grid function is well documented to indicate the existence of the function, you shouldn't have that problem. When beginning work on an established product, most of us look through the code to see how something was done and imitate that methodology as closely as possible, and chances are pretty good that you'll notice the comment about the existing grid function.
Since you know all of the properties of the grid ahead of time, the grid function can be written in such a way as to support all of its potential properties, and handle the absence of associated properties in the options object (default functionality), making the function robust and reasonably future-proof. That way, the options object only has to be initialized with properties that matter to its current implementation. It ain't hard to do or conceptualize.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
#realJSOP wrote: It ain't hard to do or conceptualize.
Famous last words! Have you visited QA recently?
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|