|
I wish people would shut up about AI and chatbots
i cri evry tiem
|
|
|
|
|
The FBI’s Next Generation Identification Biometrics Database went live nationwide in 2014 without much fanfare from the general public. That's OK, I already know what my face looks like
Do two faced people have two records?
|
|
|
|
|
Darn well better or we'll be mad yes we will.
|
|
|
|
|
What happens with people that have face transplants? Both the provider and recipient?
|
|
|
|
|
They go on to make even more terrible films[^]. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Back-end changes at Outlook.com are making the old email client obsolete How about Outlook Express?
Yes, I know the answer is in the article, but that's the only other Microsoft email client I could think of. I couldn't remember the name of the old DOS-based one. Or was it just "Mail"? Or was that just the back-end?
|
|
|
|
|
They didn't say anything about the 2011 version i may still be good 
|
|
|
|
|
No pop/imap/smtp support on one end? 
Or did they explicitly have Windows LiveDead Mail not allow you to use those because of the availability of the other 'better' interface that's now being turned off.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging 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
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Debate continues on whether employers consider a high rank on developer community sites like Stack Overflow when deciding who to hire. blah blah blah Betteridge's Law blah blah (but maybe)
|
|
|
|
|
No.
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
I don't know about SO, but:
Hiring Managers May Find You Online Without Help
That is certainly true. A couple days after CP announced the 2016 MVP's, I got a call from a hiring manager. I asked him how he heard about me and he said looks at the CP MVP's. I didn't take the job (it was too far away, and we had just bought a house), but I would have definitely received an offer.
I remember a client once, several years ago, hiring a summer college intern. The intern asked who else was working on the project, to which, when told, the intern responded, "What? THE Marc Clifton???" That was a fun story to hear.
Marc
|
|
|
|
|
I believe it could aid or hinder getting a job. I try and have only a positive or agnostic reflection of myself online.
If you do well on the interview, then HR and the hiring manager would probably Google search you and see what they can find about you, maybe even preinterview. If you are a strong contributor to the IT community, I believe it would aid you. For example, many CP users post articles, tips, tech blogs, and Q&A helping the community. This is online and there for everyone to see, so it could be an aid. An aid of contribution and an aid on your technical acumen. And yes, I see some users on Stack Overflow and Code Project are cut throat in the Q&A section; so they think it helps.
If you post racial, sexist, or dirty materials online, then you probably won't get the job if they see it, even if you are in the top 10 of points for Stack Overflow or Code Project. If you are getting trolled, trolling, or are argumentative online, then it can hurt you. I only post online to sites where I can delete the entry if it comes out rough or insensitive.
* Note to self, delete in 48 hours.
|
|
|
|
|
Oh, you are very active on CP / SO and the like. Great skills!
But what about your boss? Didn't he expect you to work for him while you were on those sites?
Ehm,...
|
|
|
|
|
This is the hypothetical puzzle set by René Heller, an astrophysicist at the Max Planck Institute Solar System Research (MPISSR). "All I see now is blonde, brunette, redhead."
|
|
|
|
|
Most of it is ads. They're wanting to know if we have a good ad blocker they can use.
Marc
|
|
|
|
|
Skip this planet, there's no intelligent life here.
New version: WinHeist Version 2.2.2 Beta I told my psychiatrist that I was hearing voices in my head. He said you don't have a psychiatrist!
|
|
|
|
|
A team at Carnegie Mellon has found a way to make skin a user interface for gadgets I was just trying to select some text. Honest!
|
|
|
|
|
Kent Sharkey wrote: I was just trying to select some text. Honest!
Knobs not included.
|
|
|
|
|
Using digital platforms such as tablets and laptops for reading may make you more inclined to focus on concrete details rather than interpreting information more abstractly, according to a new study. Eh, let me think about it
|
|
|
|
|
Preview users can test out extensions for the new Microsoft has released the latest edition of its twice-annual Security Intelligence Report, its survey of the security landscape and threats around the world. The survey has a ton of data about what malware is infecting people, which parts of the world are seeing increased attacks, and more. "Evil is not a view ... it's an ingredient in us. In the world. Poured over us, filtering into our bodies, minds, hearts, into the pavement itself."
|
|
|
|
|
Preview users can test out extensions for the new Windows web browser. Now you can browse like it's 1999
|
|
|
|
|
Microsoft is now aiming to release its cross-platform Web-development framework, ASP.NET Core 1.0, by June 2016. Not to be confused with regular ASP.NET 4.6
|
|
|
|
|
Every good comes with a bad. Here's why agile software development won't solve all your problems. There's always a downside.
|
|
|
|
|
On the basis that this isn't another oh-so-brilliant retrospective LOLZ post I would offer the following:
<quote>
1. Less Predictability
The more regimented, waterfall process makes it easy to quantify effort, time, and cost of delivering the final product.
It doesn't make it easy at all but it does make it compulsory. Note that a compulsory guess is still a guess and what happens in waterfall practice is that the estimate undergoes a magical transformation to becoming a deadline and as such is used to reward project managers and beat up developers. That never works out particularly well.
2. More Time and Commitment
Testers, customers, and developers must constantly interact with each other.
Yes - they must. The article seems to present this as a bad thing. Not to be overly flippant but walking slowly in the right direction is vastly preferable to running in the wrong direction.
3. Greater Demands on Developers and Clients
These principles require close collaboration and extensive user involvement. ...it demands a big commitment for the entirety of the project to ensure success.
Commitment is a good thing in business. "Fire-and-forget" management is to be found in almost any news story that contains the line "..decided to scrap the multi-million dollar project without realising any benefit..." or "..costs spiralled out of control.." Any project that consists of "These are my needs and here is some money. I'll expect to see the results in two years time" is (and has frequently been) a time bomb.
4. Lack of Necessary Documentation
Less documentation, certainly - but less "necessary" documentation? I'd prefer two sentences that were factually correct and were kept up to date with any changes to the project in place of two hundred binders of documentation that were neither.
5. Project Easily Falls Off Track
If it does this is not an Agile thing, it is a weak management thing...and Agile is more suited to a gated-delivery process which keeps projects on track than Waterfall is.
There are valid concerns with Agile but I think Agile is Dead • Pragmatic Dave Thomas - YouTube[^] is a better resource than this article.
|
|
|
|
|
Not that I'd ever defend Agile, but like Duncan, let's take these one at a time:
- Less Predictability
Developers can rarely quantify the full extent of required efforts, because 1) there are so many details that have not been communicated 2) many (even small) efforts get only one side of the requirement story. The cliche "history is written by the victors" is also true of specs. Specs are written from the perspective of that user."
The more regimented, waterfall process makes it easy to quantify effort, time, and cost of delivering the final product.
And the more likely that what gets delivered isn't what is wanted because the development effort is a black box. Here's the spec, go away for 6 months or 6 years, come back with the product. It may meet the specs, but little else.
- More Time and Commitment
This is a joke. It's isn't more time and commitment, it's better time, making minor course corrections early on rather than expensive, time, $ and energy consuming, major course corrections later on. We don't just launch a satellite by pointing the rocket anywhere. And during the rocket's flight, it's flight path constantly undergoes minor corrections. Imagine the amount of fuel you'd have to hoist into orbit to fix the deviation after the fact.
- Greater Demands on Developers and Clients
Again, more conscious, up front, demands on communication and review means less demands on the lawyers later on to clean up the mess.
Clients must go through training to aid in product development. Any lack of client participation will impact software quality and success.
Deliver a product that the client has never seen, spec'd by someone that may not even have been the client, and yeah, you have an impact on quality and success.
- Lack of Necessary Documentation
Agreed -- the agile experiences I've participated in were poor on documentation. However, the non-agile experiences I've had were also poor on documentation, perhaps even more so.
- Project Easily Falls Off Track
Agile is not unique to this problem, and if done right, can better avoid it.
It also has the potential for scope creep, and an ever-changing product becomes an ever-lasting one.
Again, not unique to agile, but what becomes more apparent to everyone is the impact on upcoming sprints and overall due dates. It also lets the developer determine whether the scope creep can be handled by temporarily adding a person or two to the project or outsourcing the work, and still keep on track. Not unique to agile, but at least there's more conversation (from what I've seen) regarding scope creep.
This method is not beneficial when the client must work on a specified budget or schedule.
Ironically, that's when I've seen it work best (when it works) because the developers must come up with concrete tasks, sub-tasks, and estimate the sprints to complete those tasks. You very quickly discover, before any coding is done, whether you're within the budget and the schedule. Then again, doing it any differently, whether you call it agile or not, is ridiculous.
At the end of the day, whether you're using the waterfall myth or agile (which nobody that I've ever encountered actually knows how to do) the success of a project depends on communication, which depends on good people, not methodologies to compensate for bad people.
Marc
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
