Tag: tech

Mar 27
longtext posts

No one is saying that all stories, or even most will be written by computers, but it’s not difficult to imagine that a good number of them will be simply because most stories today have significant chunks that aren’t deeply reported. They’re cribbed from press releases, interpreted from box scores or condensed from the wire. If we leave the drudge work to the computers, we can free up reporters to do things that computers can’t, and actually producing more, better content. It’s quite literally win-win. The primary losers are those companies who will buy too deeply into the idea that they can generate all their content automatically.

We've been arguing about AI stories since 2014

I still wholeheartedly think that entirely generated content is essentially useless to end-users.

Mar 11
longtext posts

What we wanted was an easy way to get photos from any device (photographers frequently work using only their phones or tablets, because it’s one less and/or lighter piece of equipment they have to lug around versus a laptop) and push it to three places — the web, print and our archive. The simplest solution seemed to be getting the file into our system and then moving it around from there.

Enter Dropbox. It’s extraordinary how even free services can do what used to require expensive services that were frequently more unreliable. Using the free 2GB Dropbox plan, we made sure that all of the devices were syncing to the same account, as well as to the “new” automater machine.

Find out how we synced on no budget

This would be much easier nowadays, as you'd just have a cloud-based Digital Asset Management system, but the budget would also be MUCH higher.

Nov 23
longtext posts

Again, I understand the basic impetus behind this line of thinking. But it fails on two levels, both of them human. One: If you make it in the employee’s best interest to not share vital strategic or business information with a competitor, that employee (provided he/she is acting rationally) will not do so. This worry is, at heart, an admission that a company is not providing its employees with the proper incentive to act against the company.

Security depends on how much you can trust your users, not how well you can lock them down.

Unfortunately, the ubqiquity of surveillance capitalism has pushed people strongly in the direction of control over trust.

Aug 13
photo posts

The one "published" joke I've ever had was when I submitted a joke review for Codekit 3. Proud of it to this day, even more so because mine was the only joke that got through from the beta-testers.

Aug 13
longtext posts

This problem was compounded when we decided on the scope of the project Our high school football coverage is run by GameTimePA, which consists of the sports journalists from the York Daily Record, Hanover Evening Sun, Chambersburg Public Opinion and Lebanon Daily News. The four newsrooms are considered a "cluster," which means that we're relatively close geographically and tend to work together. Since the last preview, however, GameTimePA had expanded to include our corporate siblings in the Philadelphia area, meaning we now encompassed something like 10 newsrooms stretching from Central Pennsylvania to the New Jersey border.

And we're all on different CMSes.

How ever will this dilemma be solved? I bet they use code
Jul 23
longtext posts

These are what we’ll call sensible (though regrettable) redundancies. But the problem with technological innovation is that we think that any problem, with enough sufficient amounts of tech wizardry thrown at it, will disappear.

The flaw with this philosophy is that, much as with medicine and side effects, sometimes the troubles with the cure are worse than the problem it was trying to solve.

You can't have sentience without self-doubt

This seems especially true in the age of AI.

Jul 13
text posts

Rarely is the question asked, "Is our children tweeting?" This question is likely nonexistent in journalism schools, which currently provide the means for 95+ percent of aspiring journalists to so reach said aspirations. Leaving aside the relative "duh" factor (one imagines someone who walks into J101 without a Twitter handle is the same kind of person who scrunches up his nose and furrows his brow at the thought of a "smart ... phone?"), simple (slightly old) statistics tell us that 15% of Americans on the Internet use Twitter.

(This is probably an important statistic for newsrooms in general to be aware of vis-a-vis how much time they devote to it, but that's another matter.)

For most journalism students, Twitter is very likely already a part of life. Every introduction they're given to Twitter during a class is probably time better spent doing anything else, like learning about reporting. Or actually reporting. Or learning HTML.

I know this idea is not a popular one. The allure and promise of every new CMS or web service that comes out almost always includes a line similar to, "Requires no coding!" or "No design experience necessary!" And they're right, for the most part. If all you're looking to do is make words appear on the internet, or be able to embed whatever the latest Storify/NewHive/GeoFeedia widget they came out with, you probably don't need to know HTML.

Until your embed breaks. Or you get a call from a reader who's looking at your latest Spundge on an iPad app and can't read a word. Or someone goes into edit your story and accidentally kills off a closing </p> tag, or adds an open <div>, and everything disappears.

Suddenly it's "find the three people in the newsroom who know HTML," or even worse, try to track down someone in IT who's willing to listen. Not exactly attractive prospects.

Heck, having knowledge of how the web works would probably even help them use these other technologies. Not just in troubleshooting, but in basic setup and implementation. In the same way we expect a basic competence in journalists to produce their stories in Word (complete with whatever styles or code your antiquated pagination system might prescribe), so too should we expect the same on digital.

Especially in a news climate where reporters are expected as a matter of routine to file their own stories to the web, it's ludicrous that they're not expected to know that an <img> tag self-closes, or even the basic theory behind open and closed tags. No one ever did their job worse because they knew how to use their tools properly.

I'm not saying everyone needs to be able to code his or her own blog, but everyone should have a basic command of their most prominent platform. It's time we shifted the expectations for reporters from "not focused entirely on print" to "actually focused on digital."

Permalink

Thanks to Elon, no asks if our children are tweeting anymore. There's a big advantage in learning how to use all your tools properly, even if it doesn't seem like it.

Sep 17
longtext posts

People who have seen new technology come into use view the technology only in terms of its functionality, a means to an end. Cellphones (and smartphones) are not their lifeline to life itself, they're a means of communication. Sure, they'll learn how to Facebook on the go, post Instagrams to Twitter and message their unruly teen to make sure he gets home before curfew, but if you took it away they'd still survive. They've got paper address books, landlines and actual (still digital, usually) cameras that aren't grafted onto a phone.

Nobody over 35 reads blogs anymore

I remember being vehemently anti-smartphone and then, after I caved and bought an Android, anti-Apple. Now I'm pretty much anti-everything new, except I also want the fastest, prettiest devices. I'm basically the worst.

Sep 20
longtext posts

Hoo boy! As a [technology writer/reporter without a story idea/old person], I've seen my share of changes in life. But [new product] is about to completely alter [area in which new technology will have extremely slight impact].

[witty teaser to get you to read more]

Replace "Nicholas Carr" with "John Hermann" and this was accurate through about 2023.