tech article ’21
Introduction
If you could read one and only one ESSAY to learn about the state of Information Systems in the world and in business, then this is the one:
Ford, P. (2015, June 15). Code: An Essay. Bloomberg Businessweek, 4431, 13–110.
Together with a partner,
- summarize THREE total chapters (one per column + one from random list),
- write a quiz question for each, and generate a list of facts.
- Then, write your own chapter with new or different content.
- Lastly, create and update the TIMELINE with facts and details from all 4 chapters.
- NOTE: That is ALL Three Parts (summaries, chapter, & timeline) with the same partner.
Submit via CNVS tech-story-partners
- only one partner needs to submit provided that you have both joined a tech-story-partners group
- CNVS > People > tech-story-partners
The Essay: CODE?
The What is Code? issue of Bloomberg Businessweek from June 15, 2015 is a collection of 41 short articles (or chapters) written by Paul Ford.
Henceforth, I’ll call this resource: “CODE?”
You can find it in a variety of places and formats:
- CODE? via Bloomberg: interactive activities throughout
- (like a GIF of a sweaty Steve Balmer of Microsoft.)
- (I saw him once in 2001 when I was a consultant up at MS HQ in Redmond, WA)
- (Whoa, strong flex, Dr. Cumbie)
- CODE? as a scanned/downloadable PDF
- can’t CTRL-F search & not screen-reader compliant
- Search for it at UNA Library
- query: JN “Bloomberg Businessweek”
- then > Full text access > Business Source Complete
- scroll way down on right side of issue list
- expand: [+] Jun 2015
- click: Issue 4431 – 6/15/2015
- each chapter listed as its own entry, can’t view it all at once.
Article Selection
CODE? has 41 “articles” (or chapters, sections, whatever)
Pick one from each column (CODE?, p. 15)
- chose one from pp. 17-70
- chose one from pp. 71-109
The choice is up to you. If you pick one that doesn’t fit well with the assignment requirements, go back to and pick another!
Lastly, choose one from this list:
Click to Expand
- tech-story-group —> CODE? Chapter
- 1 > 10/Why are Programmers So Intense About Languages?
- 2 > 6/How Does Code Become Software?
- 3 > 33/Nothing Is Built
- 4 > 5/From Hardware to Software
- 5 > 3/Let’s Begin
- 6 > 39/Managing Programmers
- 7 > 7/What Is an Algorithm?
- 8 > 27/Off the Shelf
- 9 > 26/Liquid Infrastructure
- 10 > 41/Should You Learn Code?
- 11 > 4/How do you type an “A”?
- 12 > 15/Look How Big and Weird Things Get With Just Python
- 13 > 9/What’s With All These Conferences, Anyway?
- 14 > 21/The Time You Attended the E-mail Address Validation Meeting
- 15 > 2/Why Are We Here?
- 16 > 20/Why Are There So Many Languages?
- 17 > 41/Should You Learn Code?
- 18 > 22/What Is the Relationship Between Code and Data?
- 19 > 25/Briefly on the Huge Subject of Microsoft
- 20 > 16/Why Are Coders so Angry?
- 21 > 8/The Sprint
- 22 > 36/The Triumph of Middle Management
- 23 > 32/What is Debugging?
- 24 > 11/The Beauty of a Standard Library
- 25 > 34/How Does Testing Work?
- 26 > 30/How Are Apps Made?
- 27 > 35/And Now for Something Beautiful
- 28 > 18/The Thing About Real Artists is That They-
- 29 > 12/What do Different Languages Do?
- 30 > 1/The Man in the Taupe Blazer
- 31 > 28/What About JavaScript?
- 32 > 40/“We Are Going to Ship”
- 33 > 37/How Do You Pick a Programming Language?
- 34 > 19/We Still Need to Choose…
- 35 > 29/What is the Absolute Minimum I Must Know About PHP?
- 36 > 23/Where Does Data Live?
- 37 > 38/Welcome to the Scrum
- 38 > 35/And Now for Something Beautiful
- 39 > 13/The Importance of C
- 40 > 2/Why Are We Here?
- 41 > 27/Off the Shelf
- 42 > 31/The Framework: Wilder, Younger Cousin of the Software Development Kit
- 43 > 14/The Corporate Object Revolution
- 44 > 19/We Still Need to Choose…
- 45 > 24/The Language of White Collars
- 46 > 35/And Now for Something Beautiful
- 47 > 4/How do you type an “A”?
- 48 > 17/The Legend of the 10X Programmer
- 49 > 26/Liquid Infrastructure
- But we already picked the RANDOM one!
NBD. Just go up or down one on the list
- Our random one is JUNK. There’s not enough content in it to complete this assignment.
NBD. Just go up or down one on the list
Working with a Partner
- How?
- That’s up to you: Zoom, MS Teams, CNVS Group Page, Google Doc (😍), Email MS Word versions back and forth.
**EXPAND THIS** to read about PARTNER INSURANCE.
- RARE but not fun when it does occur.
- Partner is a non-responsive freeloader, rolling the dice on an assignment that is 25% of their grade.
- DOCUMENT progress and contributions.
- work on a shared platform (like Goooooogle Docs) that tracks full revision history and who did what.
- Heck, even attaching docs back and forth
- Let me know early! I will drop your partner out of your group and permit you to find someone else or submit individually. This is not to be done casually.
- Keep in mind, we are all busy and on different orbits and schedules.
- Give ample time windows and a quick phone call is better than pushing back a Zoom meeting another week.
- Work async: if you define your tasks, then you can work and “handoff” (just like DevOps). “I’ll summarize the first two this morning, you can read over and edit tonight & add in the third summary.”
Instructions
TIP: Look ahead to the Submission instructions. You are limited to a CNVS Text Input box for formatting. When writing focus on Clarity & Content
Three ARTICLE SUMMARIES
Instructions also on the CNVS assignment submission.
Click here for ARTICLE SUMMARY Instructions
a) Write an EXECUTIVE BRIEF. Bold & Underline all important terms (from part b).
TIPS: Include key points from the article but do not simply restate them. Provide some insight that addresses: Why should we care? What a manager needs to know?
b) List and define/describe all dates, facts, terminology. You may need to consult some other source; cite it if you do. Wiki is cool (Like Ford says in CODE?).
c) Write a question that you’d put on an exam: multiple choice/answer, matching, short answer (no essay or true/false). Provide feedback to that question, i.e., what a student would see as guidance if they missed that question.
EXAMPLE:
Review of Chapter 2: “Why Are We Here?”
a) Executive Summary
- about a paragraph here, bullet points are good.
- lead in with your insight/interpretation of why this is important and what we need to know from this.
- when mentioning terms, facts, and other that are included in part (b), underline and boldface them
b) Glossary
- 1986 – the year of my silver convertible Chrysler LeBaron
- Somebody – invented something, started a company, and probably good at juggling too
- tech stuff – some programming language or platform or product
- organization – some company or government or department
- socio/cultural stuff – developers think they are sooooo cool
- management stuff – how we run companies
c) Question
Can I kick it?
a) yes you can (correct answer)
Explanation: ttps://www.youtube.com/watch?v=O3pyCGnZzYA
THEN REPEAT TWICE MORE
DIY (Do-it-yourself) ARTICLE
Instructions also on the CNVS assignment submission.
Click here for DIY ARTICLE Instructions
Write your own article, in the same style as CODE? with a punchy, oddly-specific title.
- You may tell about a personal experience, an instance at work something you’ve heard about or observed.
- I suggest changing names of people and companies for confidentiality
- You can pick from one of Cumbie’s old lectures
- some are audio-only, some are text only
- CODE? is so 2015. You can find something new and shiny…like:
- “Bitcoin, Bitcoin, Bitcoin!”
- “That Time GameStop Broke Wall Street”
- “React.js. Not just another framework”
- “Columnar Databases”
- “Remember When Healthcare.gov Flopped”
- Your story can be management/culture-based or technical-based.
- It can cover a specific, illustrative event like this Rookie coding mistake prior to Gab hack came from site’s CTO or something in general like: DevOps.
- Here are some title samples that I came up with:
- “that time the important email went to spam”
- “when Joe replied all to the entire company”
- “why you should (or shouldn’t care) about text message encryption?”
- “Your mother and I want to have a serious talk with you about Bitcoin”
- Length and tone should be similar to a CODE? Chapter.
- Define/Describe all terms/facts/people/places
- Find sources and cite when needed (let’s say, at least 2 sources)
- Write your own quiz question with an explanation
TIMELINE
Instructions also on the CNVS assignment submission.
Click here for TIMELINE Instructions
- CREATE a timeline computing history
- There are several overlays of timelines, eras, and all, in different sets of completion.
- Use these (or find BETTER resources out there)
- To create a general TIMELINE of the History of Computing.
- Recommend doing this in an outline form.
- Level of Detail: I’d recommend somewhere from 3-5 general eras, with dates, and just a few major categories under each.
- Then, UPDATE the timeline with at least TEN facts, some from each of the FOUR articles (three reviewed plus your own).
You are somewhat limited to what you can submit via CNVS, I believe text-based only but you can try to paste/upload in other media.
Submission
- Submit via CNVS Assignment. Each part of the assignment has its own text-input area (uploads allowed on TIMELINE)
- DO NOT WRITE YOUR ANSWERS DIRECTLY INTO CNVS. It will not auto-save. It will glitch. It’s a web-based form. Instead:
- Write offline or in something cool like a Google Doc.
- When ready to submit, copy/paste into CNVS and clean up formatting as needed.
- I think you can upload images too if you choose for your timeline or otherwise.
- Use Grammarly
Cumbie Tech Article Summaries
Criteria | Ratings | Pts | ||||||
---|---|---|---|---|---|---|---|---|
This criterion is linked to a Learning OutcomeINSTRUCTIONSCovered 3 articles: one per column + random. |
|
5 pts |
||||||
This criterion is linked to a Learning OutcomeFORMATClear & Organized |
|
5 pts |
||||||
This criterion is linked to a Learning OutcomeSummary #1Understood & get the gist without having to read the article. |
|
5 pts |
||||||
This criterion is linked to a Learning OutcomeFacts #1Understood, complete, explained. |
|
5 pts |
||||||
This criterion is linked to a Learning OutcomeQuestion #1Understood, complete can answer from article. |
|
5 pts |
||||||
This criterion is linked to a Learning OutcomeSummary #2Understood & get the gist without having to read the article. |
|
5 pts |
||||||
This criterion is linked to a Learning OutcomeFacts #2Understood, complete, explained. |
|
5 pts |
||||||
This criterion is linked to a Learning OutcomeQuestion #2Understood, complete can answer from article. |
|
5 pts |
||||||
This criterion is linked to a Learning OutcomeSummary #3Understood & get the gist without having to read the article. |
|
5 pts |
||||||
This criterion is linked to a Learning OutcomeFacts #3Understood, complete, explained. |
|
5 pts |
||||||
This criterion is linked to a Learning OutcomeQuestion #3Understood, complete can answer from article. |
|
5 pts |
||||||
This criterion is linked to a Learning OutcomeOverall QualitySubjective & relative to other submissions |
|
5 pts |
||||||
Total Points: 60 |