|
MadMyche wrote:
Back in the 90's you actually purchased software to browse the web.
Netscape was free for a long time and even after they tried to charge, people stopped using it. I don't know anyone who actually paid for it. I do remember how the version around 96/97 would leak just sitting idle.
|
|
|
|
|
MadMyche wrote: Where would we be now if we the companies (MS, Google, et al) charged for the browsers instead of spying on our every move?
Still using IE 2.0? (or maybe 5)
Hurrah for
<blink />
TTFN - Kent
|
|
|
|
|
Developers are still working—and for some, working from home is their status quo. But now, even those developers who usually work from home are finding that they have new “coworkers” with schools and other workplaces shut down. The refrigerator
|
|
|
|
|
Kent Sharkey wrote: The refrigerator
The right answer, but it really needs an echo effect and 1950s spooky movie background sounds.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Eclipse Theia combines some of the best features of IDEs into one open source extensible platform. For those who like editing code, without using 'm', 's', 'f', or 't'
|
|
|
|
|
The year of the Linux desktop may one day come.
The year of the Eclipse IDE? Never in a million years.Eclipse Theia combines some of the best features of IDEs Good luck guessing what they've renamed them and finding where they've hidden them.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Oh, thanks. You just made me choke on my pie. Far too accurate. ![Rose | [Rose]](https://www.codeproject.com/script/Forums/Images/rose.gif)
TTFN - Kent
|
|
|
|
|
Is that a VS Code screenshot? 
Those icons on the left are exactly the same (except Microsoft has updated their icons, of course), the blue bar on the bottom is the same, the colors are the same, overall look and feel is the same...
It even supports "VS Code Extension protocol" so I wouldn't be surprised if this were a copy of VS Code and then ported to the browser.
|
|
|
|
|
The system, called AutomataSynth, allows software engineers to tap into the power of hardware accelerators like FPGAs without specialized programming knowledge or needing to rewrite old, CPU-centric code. They (re)invented code libraries?
Or am I (probably) misinterpreting what they're up to?
OK, after watching the video, it seems like I've misinterpreted their methodology anyway.
|
|
|
|
|
Looks like it's more from the "Let's use the GPU to do everything..." movement, which is largely promoted by people who are too dumb to realise that "... Except its job!" is missing from the end of their sentence.
Sure, it could be said that the GPU and other hardware elements are underused a lot of the time, but if you bake this kind of cr@p into libraries, those libraries will be used by programs that do make a lot of use of the hardware that you're using to do the wrong things.
To put it another way:
You might think that misusing hardware components is a stupid thing to do, but I couldn't possibly comment*.
* If you haven't watched the original House of Cards[^], drop what you're doing and watch it right now!
I wanna be a eunuchs developer! Pass me a bread knife!
modified 31-Mar-20 0:40am.
|
|
|
|
|
In the newly released Linux 5.6 kernel, you'll finally find the long anticipated open-source Virtual Private Network, WireGuard. My wires feel safer already
|
|
|
|
|
Donenfeld said: On the backports front
Because that's how Linux wallahs speak -- and the don't do it for fun/satire/a laugh, like I do; it's all completely deadpan.
When I advertise for a partner for my double act, I'm going to put "30 years' experience in Linux development" as a requirement. Just the kind of straight-man I need.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
People talk about adopting more Agile practices and using a DevOps-centric culture, but development teams regularly say that testing is a bottleneck. I thought Agile folk didn't test?
It all just gets bumped to the next sprint.
|
|
|
|
|
I've never worked on an agile team where testing was the bottleneck, because no-one on any of the teams I've worked on was so stupid as to not understand that if something isn't tested it's not ready for release.
Testing isn't a bottleneck, it's part of the process. Not tested = not ready for release.
n.b. I've never worked for microsoft, but you probably already figured that out.
The article writer asks: who wants to kneecap the developers?
You want me to start a list?
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: I've never worked on an agile team where testing was the bottleneck
...says someone who has never worked with an agile team 
|
|
|
|
|
F-ES Sitecore wrote: ...says someone who has never worked with an agile team
Correction: says someone who has worked with more than a dozen agile teams.
If your team's doing it wrong, don't assume everyone else's is.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
It's not a matter of right or wrong, it's reality. I've also worked with countless agile teams and this is always how it has been with testing. If you are saying you have worked with dozens of teams and they haven't had this issue then I find that hard to believe.
|
|
|
|
|
Believe what you like, but if testing is properly integrated as part of the sprint, and you've got professional testers and continuous testing, there is no reason (other than tests failing, which you can hardly blame on the testers, and which should be planned for) why testing should be a bottleneck.
Problems with sprints being improperly planned can't be blamed on the testers, either. Everyone knows that everything has to be tested, so no-one has any excuse if there isn't time for testing or if devs are twiddling their thumbs waiting for tests.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I explained in my reply to the OP why testing becomes a bottleneck. The fact that this article was written in the first place is because testing becomes a bottleneck. Again I'm not saying what is right or wrong, I'm just saying what happens in the real world, something these "advice" articles never address.
|
|
|
|
|
This article exemplifies one of the problems with agile. All of the advice given for "real" problems is theoretical, it doesn't work in the real world with real people. The advice in this article would work if you have a team of developers, some of who are in charge of testing, but that is never the case. In the real world testers are people that have fallen into the job with no real technical expertise, certainly no programming skills. Obviously that's not always the case, in my career I have seen one or two testers that got into writing automated tests but it's definitely the exception and not the norm.
So you have a developer that develops, then while the testers are testing the developer works on the next ticket, then at the end of the sprint all development is done and the devs do nothing while the testers are testing. If you want to solve this problem then don't give advice on what testers can be doing, that's tackling it from the wrong direction as testers can rarely even tie their own shoes....you need to give advice on what developers can be doing while testers are testing.
|
|
|
|
|
So don't hire testers who can't create automated tests.
It's a major part of the job, so why on Earth hire people who can't do it?
You might as well hire devs who don't know any programming languages (e.g. straight from university).
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: So don't hire testers who can't create automated tests.
That's just not practical, the majority of testers can't.
Let me guess though...all the testers you know are also coders 
|
|
|
|
|
F-ES Sitecore wrote: Let me guess though...all the testers you know are also coders
Some, but by no means all. they're just people who are good at their job -- you know, the kind of people that you give jobs to.
If you're working with testers (and maybe planners, from the looks of it) who can't do the job, either get 'em trained up or get 'em transferred to jobs they can do.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Again you're talking about best-case scenarios. Obviously if you can hire nothing but the top talent then you have less problems...who doesn't want to do that? I'm talking about the real world though, which is why a lot of the "advice" given on agile isn't much use, as it ignores how things really are.
|
|
|
|
|
I didn't say "top talent". If you don't hire people who are competent to do the job they are hired to do, you've got no right to complain when they don't do it.
I don't see having competent staff as a "best-case scenario"; I see it as "business as usual".
And I'm somewhat dumbfounded that you can think otherwise.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
