|
This post is meant to provide that additional context for the principles we use to make decisions for each language. You should consider it as guidance, not as a roadmap. "The essence of strategy is choosing what not to do."
|
|
|
|
|
The issue escalated into emergency database maintenance after data was deleted accidentally — followed by an apparent inability to restore the data from backups "I don't think there is any question about it. It can only be attributable to human error."
Hurrah, for "the cloud"
|
|
|
|
|
The affected database includes issues and merge requests but not repositories
Whew! My code has no issues, and nobody but me works on it, and I have no idea how to do merging, so everything is on the master branch anyways! 
Marc
|
|
|
|
|
|
The package provides tools and scripting supported, but Python does not become a first-class CLR language The world was waiting for this
And by "waiting", I of course mean, "working away, never suspecting someone felt this was necessary".
And yes, there's still IronPython. Someone other than the developer might even use it some day.
|
|
|
|
|
Note that this package does not implement Python as a first-class CLR language -- it does not produce managed code (IL) from Python code,"
Damn. I was hoping I could take Python generated IL and decompile it to C#. 
Marc
|
|
|
|
|
I think you might be able to do that with IronPython... but don't quote me on that...
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
So, it's basically the equivalent of pinvoking the Windows API from .Net --- only it's pinvoking .Net from CPython.
 Why? Just why??
Use C#. It can already do that without the pinvoke!!! Gaaaahhhhhh.
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
As much disparity as there is between an Altair 8800 and a modern personal computer, looking even further back is fascinating. For those who long for "the good old days"
|
|
|
|
|
I still have my ENIAC running.
It really generates a huge kWatt / hour bill but it's definitely worth it.
When all the smart phones crash and the Internet fails, who'll be right then?
|
|
|
|
|
Probably keeps the house nice and toasty as well.
TTFN - Kent
|
|
|
|
|
Those were the days, my friend
We thought they'd never end
When programs ran forever and a day
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Quote: There were 5 million hand-soldered joints!
That was a lot of cigarette breaks!
Sudden Sun Death Syndrome (SSDS) is a very real concern which we should be raising awareness of. 156 billion suns die every year before they're just 1 billion years old.
While the military are doing their part, it simply isn't enough to make the amount of nukes needed to save those poor stars. - TWI2T3D (Reddit)
|
|
|
|
|
It can tell whether a completely paralyzed person is thinking “yes” or “no” Blink once for "yes", twice for "no", three times for "Take me back to Talos IV"
|
|
|
|
|
Kent Sharkey wrote: Device reads brain activity to help locked-in people communicate
When I read that, I thought, "Oh, a way to get devs to communicate..."
And, I'm a dev.
|
|
|
|
|
A Dimension Data survey of development professionals found most enterprises have adopted agile methods, but only 14% can update hourly. "Hail to the king, baby"
People want to update hourly?!
|
|
|
|
|
Well, yeah! Especially when they get paid by the same!
|
|
|
|
|
My current project takes over an hour to build and another hour or so to run automated tests, so hourly is out of the question.
|
|
|
|
|
What is your build doing that takes so long? How many unit tests does your build process run? Sounds like a very time consuming process.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
It's a very large project with cross compiler components and automated UI testing, which arguably needs even more coverage.
If you have a project of appreciable size and your automated tests only last seconds, I can all but guarantee that they are insufficient. (EDIT: This observation includes just unit tests as well. On any project of appreciable size, if your unit tests don't take up measurable time, you don't have sufficient coverage.)
modified 1-Feb-17 18:30pm.
|
|
|
|
|
Joe Woodbury wrote: if your unit tests don't take up measurable time
That's a very vague statement. What you need to ensure is that your unit tests cover
- line coverage
- functional coverage
- conditional coverage
How long they take to run depends on many different factors.
- How many other components are invoked by the unit test
- Where those components are hosted
- Network latency
- etc etc
I have an ASP.NET Web API project that has several hundred unit tests which take <10 minutes to run. This is a multi-layered architecture with many moving parts involved. These unit tests are executed with every single check-in.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
Of course it's vague since there is no absolute correct time unit tests should run. What I'm describing is a "smell" test--that unit tests should take up some noticeable percentage of your compilation (or even checkout) time. Except for the smallest of projects, unit tests should take long enough for you to remove your hands from the keyboard.
Put another way; from my observation, most unit tests aren't comprehensive enough. Even saying that you have line coverage is a piss poor way to ensure sufficient testing. Have you covered the full logic of the object being tested?
(I ran into the last point this past week. The functions in question had full line coverage. Out of habit, I added some nonsense data to the tests. The newer function passed. The existing function, which I didn't write, faulted. This behavior wasn't documented.)
Dominic Burford wrote: which take <10 minutes to run
Sounds like they take up [human] measurable time.
|
|
|
|
|
Information Week wrote: Agile is king
But the age of kings is over...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
I'll happily update/deploy hourly.
09:00 Deployed v1.6.11.
10:00 Deployed v1.6.11 again.
11:00 Deployed v1.6.11 again.
12:00 Deployed v1.6.11 again.
13:00 Lunch
14:00 Deployed v1.6.11 again.
15:00 Deployed v1.6.11 again.
16:00 Deployed v1.6.11 again.
17:00 Deployed v1.6.11 again.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Introducing small, but noticeable changes, can make the alerts more useful and harder to ignore. Because everyone appreciates stuff popping up and dancing on their screens
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
