This sounds like real progress. Areolar storage should soon reach the milestone of being able to store 80GB in one's nipples, and soon thereafter, in a single nipple. Those with polymastia and other mammals will reach this sooner.
It's a possibility. Of course, I plan to be uploaded into an AI-capable processor core a few years before then, and then delegate the taxi work to a slave node, but hey, a job's a job.
I hear they'll redo the site to update it with a more modern look. I think they'll set up a site with test modifications, and call it 'Slashdot Bis' while collecting feedback, which they expect will be nearly universally positive.
Doesn't Verizon have FIOS and/or wireless networking through converted phone booths? I didn't know Time-Warner had such a firm grip on New York's high-speed Internet access market.
I thought that using CGI would be less expensive overall. Between material/storage costs, labor costs, available physical/practical vs. computer modeling/rendering skillsets, desired visual style and/or realism, time, and other considerations, are we at a sort of intermediate point before either practical or CGI becomes a clearly better choice?
Narrative debt arises for many reasons - whether moving goal posts, pressure to get articles edited and posted, high writer turnover, and lack of organization of source material. Over time, it can also render workflow a spaghetti-like mess. But how to deal with it?
In a new column on Dice, developer David Bolton offers some suggestions, ranging from restructuring to using natural language inference to increase readability and shorten sentences. While those techniques are straightforward, it's clear that a lot of writers let their source material get out of control, and trying to plan beforehand doesn't necessarily prevent the work from getting overcomplicated. It seems like every writer has a go-to technique (or four) for keeping things a little more streamlined. What are yours?
Maria Hasankolli... came home in the early hours of the morning after visiting a relative at the hospital.... The cops... then went to his home, woke Hasankolli and clapped her into handcuffs.
I think I'll refrain from complaining about my day for the rest of this month.
After awhile, we just stop keeping track of what's legitimately good because it takes too much energy to separate the crème from the foam.
I don't know why he thinks this would be that difficult. Low-quality stuff is written in the vernacular, and truly valuable literature and discourse uses assimilated foreign words with accents unnecessarily. I'll bet that checking for the high-order bit would be good enough.
I think we all end up in a socially unhealthy environment if women have to start segregated women's projects as you suggest or if we don't get them into our communities.
I'd appreciate the existence of some women's-only projects. It would provide good visible, referrable examples, possibly separating "rough consensus and working code" from the other dynamics -- negative, neutral, and positive -- that many of us, men and women, have been living with so long that we've assumed they're naturally part of software development/engineering.
It's bad for men too if that continues to happen.
In the abstract, yes. But it would also be great to have some concrete, observable examples of where/how the architecture/project/coding dynamic separates along gender/personality/cultural lines by being able to examine multiple such real-world environments, rather than having to speculate. My own theory is that engineers have more commonalities than gender groups do -- an opinion that has little value without real-world bases for comparison.
Considering that *every* proprietary software company is a similar silo, segregated by criteria other than gender, I (IMO) doubt that having such projects in the ecosystem would have detrimental effects of that large a scale. In any case, everyone would then be able to see its concrete issues and effects, and hopefully adjust their behavior accordingly.
Nor is the problem minor, I would post a link to some of the more repulsive stuff but I don't want to promote it.
Some sanitized/anonymized stuff would be useful, along the lines of what Daily WTF provides -- people could rank their project/workplace among the observed behaviors, at least along the lines of "It's *never* been this bad anywhere I've worked," to "I see this come close occasionally," to "Yeah, this happens often enough." It could also serve to help projects consider and draft policy on specific actions they would commit to taking, when presented with similar/comparable situations.
This would mean that projects would then be making commitments on their positions, and taking responsibility for not/following through when such situations occur. On a philosophical note, this sounds synonymous to a sort of industry 'maturity' -- while not everyone will sign up for that, at least individuals and groups could know, for themselves and for others, where they stand.
On a final note, I agree that the problem isn't minor. But if the problem is defined as "a vocal minority of males behave in the most boorish, misogynistic, objectifying manner toward women", it seems that this would simply come along with being a cross-section of the general male population. If there's more to it than that -- e.g., background, social awkwardness, personality profile -- I think the problem(s) would benefit from more specific and better-addressable definition(s). I also can't help but feel that more mature industries would quickly reprimand and then if necessary, smoothly eject these people who advertise themselves so vocally. But again, I can't say for sure without other bases for comparison.
Slashdot Mirror
This sounds like real progress. Areolar storage should soon reach the milestone of being able to store 80GB in one's nipples, and soon thereafter, in a single nipple. Those with polymastia and other mammals will reach this sooner.
Oh wait, I think I misread that. Never mind.
Finally, vindication. Enough talk, let's celebrate!
I'll have to assume you didn't get the memo.
A few other things along these lines:
It's a possibility. Of course, I plan to be uploaded into an AI-capable processor core a few years before then, and then delegate the taxi work to a slave node, but hey, a job's a job.
Sure thing! Here you go.
Don't forget to (accidentally) install a compiler first.
Good thing I posted this, that could have been a close call!
Are you a nerd? If so, in what areas?
How did your parents pick the name 'Logan'?
Well, you did say *any* questions.
I hear they'll redo the site to update it with a more modern look. I think they'll set up a site with test modifications, and call it 'Slashdot Bis' while collecting feedback, which they expect will be nearly universally positive.
Perhaps, but lots of upper-level decision-makers buy based on shiny.
An *advertising* organization. Why is anyone here taking anything in that speech at face value?
Doesn't Verizon have FIOS and/or wireless networking through converted phone booths? I didn't know Time-Warner had such a firm grip on New York's high-speed Internet access market.
Isn't it closer to "Why 6 Republican Senators Are Repeating Cable ISP Lobbyists' Talking Points on Why You Don't Need Faster Broadband"?
Between that description and the name 'Theranos', this sounds like the backstory for the next version of an upcoming post-apocalyptic FPS.
I thought that using CGI would be less expensive overall. Between material/storage costs, labor costs, available physical/practical vs. computer modeling/rendering skillsets, desired visual style and/or realism, time, and other considerations, are we at a sort of intermediate point before either practical or CGI becomes a clearly better choice?
Don't forget:
11. No kids on the lawn.
retying my shoe just before going to the airport.
See? A responsible weapon and tactical boot owner.
... the seals handle marketing ...
As well as final product approval.
Narrative debt arises for many reasons - whether moving goal posts, pressure to get articles edited and posted, high writer turnover, and lack of organization of source material. Over time, it can also render workflow a spaghetti-like mess. But how to deal with it?
In a new column on Dice, developer David Bolton offers some suggestions, ranging from restructuring to using natural language inference to increase readability and shorten sentences. While those techniques are straightforward, it's clear that a lot of writers let their source material get out of control, and trying to plan beforehand doesn't necessarily prevent the work from getting overcomplicated. It seems like every writer has a go-to technique (or four) for keeping things a little more streamlined. What are yours?
Maria Hasankolli ... came home in the early hours of the morning after visiting a relative at the hospital. ... ... then went to his home, woke Hasankolli and clapped her into handcuffs.
The cops
I think I'll refrain from complaining about my day for the rest of this month.
If they can generate a level-5 seismic event from that, good for them, I guess.
4. With all the bugs fixed, you can now fire the programmers.
5. Rehire the managers.
6. Repeat!
After awhile, we just stop keeping track of what's legitimately good because it takes too much energy to separate the crème from the foam.
I don't know why he thinks this would be that difficult. Low-quality stuff is written in the vernacular, and truly valuable literature and discourse uses assimilated foreign words with accents unnecessarily. I'll bet that checking for the high-order bit would be good enough.
I think we all end up in a socially unhealthy environment if women have to start segregated women's projects as you suggest or if we don't get them into our communities.
I'd appreciate the existence of some women's-only projects. It would provide good visible, referrable examples, possibly separating "rough consensus and working code" from the other dynamics -- negative, neutral, and positive -- that many of us, men and women, have been living with so long that we've assumed they're naturally part of software development/engineering.
It's bad for men too if that continues to happen.
In the abstract, yes. But it would also be great to have some concrete, observable examples of where/how the architecture/project/coding dynamic separates along gender/personality/cultural lines by being able to examine multiple such real-world environments, rather than having to speculate. My own theory is that engineers have more commonalities than gender groups do -- an opinion that has little value without real-world bases for comparison.
Considering that *every* proprietary software company is a similar silo, segregated by criteria other than gender, I (IMO) doubt that having such projects in the ecosystem would have detrimental effects of that large a scale. In any case, everyone would then be able to see its concrete issues and effects, and hopefully adjust their behavior accordingly.
Nor is the problem minor, I would post a link to some of the more repulsive stuff but I don't want to promote it.
Some sanitized/anonymized stuff would be useful, along the lines of what Daily WTF provides -- people could rank their project/workplace among the observed behaviors, at least along the lines of "It's *never* been this bad anywhere I've worked," to "I see this come close occasionally," to "Yeah, this happens often enough." It could also serve to help projects consider and draft policy on specific actions they would commit to taking, when presented with similar/comparable situations.
This would mean that projects would then be making commitments on their positions, and taking responsibility for not/following through when such situations occur. On a philosophical note, this sounds synonymous to a sort of industry 'maturity' -- while not everyone will sign up for that, at least individuals and groups could know, for themselves and for others, where they stand.
On a final note, I agree that the problem isn't minor. But if the problem is defined as "a vocal minority of males behave in the most boorish, misogynistic, objectifying manner toward women", it seems that this would simply come along with being a cross-section of the general male population. If there's more to it than that -- e.g., background, social awkwardness, personality profile -- I think the problem(s) would benefit from more specific and better-addressable definition(s). I also can't help but feel that more mature industries would quickly reprimand and then if necessary, smoothly eject these people who advertise themselves so vocally. But again, I can't say for sure without other bases for comparison.