If you couldn't make the (nearly) back-to-back sprints on beta-blocking issues at Drupal DevDays Szeged and NYC Camp, don't worry! We still have some leftover sprint tasks that will help with the first Drupal 8 beta release. Many of the 27 remaining beta blockers require deep knowledge of the problem space; however, the tasks listed here (while not necessarily quick or easy) are more approachable and self-contained. Some of these issues are beta-blocking in their own right; others are "beta target" issues that would ideally be done for a beta release even if they aren't critical enough to block it.
If you're new to core contribution or Drupal 8, check out the Core Contribution Mentoring program instead.Documenting Critical Drupal 8 APIs #1988612: Change record: Apply formatters and widgets to rendered entity base fields
Entities in Drupal 7 and 8 have two kinds of field data: base fields (or properties in Drupal 7), like the node author field or the taxonomy term description, and configurable field instances, which can be attached to a given fieldable entity type's bundles through the user interface. Previously, it was not possible to use widgets or formatters for base fields, so they typically use custom form elements and rendering code that are not compatible with Drupal 8's in-place editing functionality. Since December, however, it is possible to use widgets and formatters on base fields -- but there is no change record yet for this improvement.#2244777: Document in WSCCI change notice or handbook all the menu changes (tasks, actions, contextual links, menu links) from 7 to 8
In order for contrib developers to make good use of our first beta release, we need good documentation of the new Drupal 8 routing and menu systems. The first step is to thoroughly document exactly how a Drupal 7 module's hook_menu() is upgraded to Drupal 8, and the exisitng change record is only partially complete. Join the discussion on this issue and help us complete this critical documentation.#2046367: Document the internals of the router
While not explicitly beta-blocking at this point, more complete API documentation for the routing system overall will be very valuable to contributed module developers using the first beta release. Help improve the routing documentation both in the Drupal.org handbook and in the Druapl 8 codebase.#2235363: Document how plugin definitions should declare config dependencies
This is a documentation followup for one small API change that supports the new configuration dependency system. It sits at the intersection of two new (and complicated) Drupal 8 APIs: plugin derivatives and the configuration entity system. Most of the confusing work for this issue is done, and it has resulted in a new handbook page on configuration entity dependencies. The remaining task is to add documentation of the config_dependencies key in plugin derivative definitions to the API documentation in the codebase. (See under "Calculating dependencies in plugins and their derivatives" on the handbook page.) The handbook page, which is about configuration dependencies generally, also needs further work, but that is not blocking for this issue.Configuration system #2224761: Translation sync should be stored in own storage instead of injected in field instance settings
This issue for the content translation module changes the way some of the module's configuration is stored. It's an easier change to implement compared to other deep architectural beta blockers for the Configuration system and the Entity Field API, but it still needs some work to resolve. The next step is to incorporate the latest feedback in comments #24 through #27 on the issue. This is also a great spot for multilingual initiative contributors to help with the beta.#2140511: Configuration file name collisions silently ignored for default configuration
This critical configuration system bug isn't a hard blocker for the beta release, but it can cause significant problems. An in-progress patch on the issue needs test failures resolved, updates for the latest changes in the configuration system, and other improvements.Entity Field API #2016679: [Meta] Expand Entity Type interfaces to provide methods
Drupal 8 core provides numerous entity types, but the full API for each type is not easily documented or discoverable, since the entity's properties are accessed through magic getters. To improve the developer experience, each entity type interface is being expanded with relevant methods for the specific entity. (For example, NodeInterface now has methods like isPromoted(), isPublished(), getTitle(), and setTitle().) All the methods for content entity types have been added, but only 1/4 of the configuration entity type interfaces are complete. Most issues have a submitted patch, and what is most needed is architectural review of the proposed interface methods. (For example, see comment #19 on the FieldConfig issue.) If you have experience with one of the subsystems that still has an open child issue, or if you have a sound grasp on OO design generally, we could use your help to thoroughly review these patches so that the completed APIs are available for contributed module developers in a beta release.#2190313: Add $EntityType::load() and loadMultiple() to simplify loading entities
In a similar vein of improving the entity system's developer experience by making the API more discoverable and removing exposure to internal concepts, this issue adds static methods for loading the entities of each type. The patch needs to be rerolled to apply to HEAD, and then needs architectural review.#2010930: [META] Apply formatters and widgets to rendered entity base fields
Remember that issue above about widgets and formatters for base fields? We also need to convert base fields other than the node title to also use widgets and formatters rather than custom code. This isn't considered beta-blocking, but it will change how contributed module developers interact with these entity types (plus make it so that in-place editing behaves in a more expected fashion). The several child issues of this meta (one per entity type) need either further work on the patch or code review. If you're somewhat familiar with entities and fields in Drupal 8, this is a good place to help.Views conversions #1823450: [Meta] Convert core listings to Views
One of the major benefits of having Views in core is that legacy one-off listings in core can be replaced with user-configurable views. Views is used in numerous places in core already, for example, the user and content administration screens, the promoted node frontpage and RSS feed, and numerous blocks like the "Recent content" and "Who's online" blocks. A handful of more complicated legacy core listings still need to be converted to views. These conversions don't block a beta release, but are targeted for the beta since adding them involves removing legacy API functions. In particular, it would be valuable to complete the conversions of the comment admin page and the taxonomy term pages to views for a beta release. Additionally, replacing the content revision table with a view is blocked on a major views bug related to content revisions.
How to find bugs in MySQL by Roel Van de Paar.
From the post:
Finding bugs in MySQL is not only fun, it’s also something I have been doing the last four years of my life.
Whether you want to become the next Shane Bester (who is generally considered the most skilled MySQL bug hunter worldwide), or just want to prove you can outsmart some of the world’s best programmers, finding bugs in MySQL is a skill not reserved anymore to top QA engineers armed with a loads of scripts, expensive flash storage and top-range server hardware. Off course, for professionals that’s still the way to go, but now anyone with an average laptop and a standard HDD can have a lot of fun trying to find that elusive crash…
If you follow this post carefully, you may well be able to find a nice crashing bug (or two) running RQG (an excellent database QA tool). Linux would be the preferred testing OS, but if you are using Windows as your main OS, I would recommend getting Virtual Box and running a Linux guest in a suitably sized (i.e. large) VM. In terms of the acronym “RQG”, this stands for “Random Query Generator,” also named “randgen.”
If you’re not just after finding any bug out there (“bug hunting”), you can tune the RQG grammars (files that define what sort of SQL RQG executes) to more or less match your “issue area.” For example, if you are always running into a situation where the server crashes on a DELETE query (as seen at the end of the mysqld error log for example), you would want an SQL grammar that definitely has a variety of DELETE queries in it. These queries should be closely matched with the actual crashing query – crashes usually happen due to exactly the same, or similar statements with the same clauses, conditions etc.
Just in case you feel a bit old for an Easter egg hunt today, consider going on a MySQL bug hunt.
Curious, do you know of RQG-like suites for noSQL databases?
PS: RQG Documentation (github)
Annotating, Extracting, and Linking Legal Information by Adam Wyner. (slides)
Great slides, provided you have enough background in the area to fill in the gaps.
I first saw this at: Wyner: Annotating, Extracting, and Linking Legal Information, which has collected up the links/resources mentioned in the slides.
Despite decades of electronic efforts and several centuries of manual effort before that, legal information retrieval remains an open challenge.
Google Genomics Preview by Kevin.
From the post:
Welcome to the Google Genomics Preview! You’ve been approved for early access to the API.
The goal of the Genomics API is to encourage interoperability and build a foundation to store, process, search, analyze and share tens of petabytes of genomic data.
We’ve loaded sample data from public BAM files:
- The complete 1000 Genomes Project
- Selections from the Personal Genome Project
How to get started:
- Follow the instructions in the developer documentation
- Try the sample genome browser which calls the API
- Try out the other open source examples — an R script, Python MapReduce, and a Java file-based implementation
- Write your own code to call the API and explore new uses
You will need to obtain an invitation to being playing.
Don’t be disappointed that Google is moving into genomics.
After all, gathering data and supplying a processing back-end for it is a critical task but not a terribly imaginative one.
The analysis you perform and the uses you enable, that’s the part that takes imagination.
From the post:
Looking for a data integration expert? Join the club. As cloud computing and big data become more desirable within the Global 2000, an abundance of data integration talent is required to make both cloud and big data work properly.
The fact of the matter is that you can’t deploy a cloud-based system without some sort of data integration as part of the solution. Either from on-premise to cloud, cloud-to-cloud, or even intra-company use of private clouds, these projects need someone who knows what they are doing when it comes to data integration.
While many cloud projects were launched without a clear understanding of the role of data integration, most people understand it now. As companies become more familiar with the could, they learn that data integration is key to the solution. For this reason, it’s important for teams to have at least some data integration talent.
The same goes for big data projects. Massive amounts of data need to be loaded into massive databases. You can’t do these projects using ad-hoc technologies anymore. The team needs someone with integration knowledge, including what technologies to bring to the project.
Generally speaking, big data systems are built around data integration solutions. Similar to cloud, the use of data integration architectural expertise should be a core part of the project. I see big data projects succeed and fail, and the biggest cause of failure is the lack of data integration expertise.
Even if not exposed to the client, a topic map based integration analysis of internal and external data records should give you a competitive advantage in future bids. After all you won’t have to re-interpret the data and all its fields, just the new ones or ones that have changed.
A hardship fund designed to protect the poorest was devolved to councils last April. Since then, spending and the number of people being helped have gone down. What has happened?
Local welfare assistance is the social safety net for Britains poorest and most vulnerable citizens, intended to provide them with vital support when they face a short-term emergency or cash crisis.
Introduced in April 2013, it replaced the social fund, the centrally-administered scheme abolished under the 2012 Welfare Reform Act. A portion of the money previously allocated to the social fund (around £178m in 2013-14) was redistributed by the Department for Work and Pensions (DWP) to 150 English councils, and to the Welsh and Scottish national governments.
Government changes to the social fund have created an emergency assistance postcode lottery that risks pushing vast numbers of the poorest families into the hands of high-cost money lenders and deeper into debt.
By denying help to those most in need, many more families will become trapped in a vicious spiral of debt and despair.Continue reading...
When it comes to Drupal base themes, it seems the conversation is often limited to which one you should choose, rather than discussing whether you should be using one at all. As someone who has spent a lot of time extolling the virtues of base themes, I thought I'd share the other side of the argument and ask if we should we use contributed base themes in our projects.
This discussion is really part of a larger debate that front-end developers are having about CSS and grid frameworks in general (see here and here), but it seems particularly relevant when discussing Drupal base themes because all of the issues are magnified due to added complexity.Why We Use Base Themes
Why do so many of us use base themes? The easy answer is that they can save us time and potentially make us more efficient. Sometimes they can also act as common ground for development teams. But I think a more complete answer is that they act as a useful crutch, particularly when first learning Drupal theming or responsive design.
At some point we all had to build our first Drupal site or our first responsive site - probably under deadline - and we looked to a base theme or framework for help. It allowed us to get the job done on time and within budget, but perhaps without fully understanding everything that was going on under the hood.
Over time we probably learned most of the base theme and developed a deeper understanding of responsive design, but the framework eventually became a comfortable place. We stuck with it, happily soldiering on until one day...When the Shortcut Becomes the Long Way
If you've been working with base themes for a while, the moment has certainly come when you have found yourself fighting with it. By design, base themes and other frameworks are opinionated - they make decisions about how to solve certain problems. Most of the time this is a good thing. It can help you accomplish things more quickly. Until it doesn't, and then your base theme is actually slowing you down and causing problems.
Part of the reason why this happens is that the developer doesn't have full mastery of the base theme - or underlying concepts - and therefore doesn't know why something is happening. This is bound to happen with base themes like Omega and Zen that are complex and have a very granular file structure, lots of hooks, etc. It can take some effort to track issues down.
Other times it's not mastery as much as the choices being made by the base theme don't match up with the project at hand. You find yourself at cross purposes with the base theme, possibly even trying to sort out incompatibilities between the base theme and a module you want to use.
And all the hacks you add to sort things out? More kilobytes that have to be downloaded by a user on a mobile device.Fast Sites Win the Day
This leads us to another reason you might not want to use a base theme - it will probably slow down your site vs a theme that is tailored for a specific project. The case has been definitively made that faster sites are more successful sites (see here and here). In most cases, base themes are going to include a lot of stuff that you are not going to need on a given project. The 'extra' stuff is bloat that will end up slowing your site down.
This isn't a slam on base themes. Most of them are akin to a Swiss army knife. They have things in them that help accomodate a lot of different scenarios - they're flexible. This can be a big help if you're a beginner, but what if you're a seasoned front-end developer tasked with building a high performance site?
In that case, maybe a base theme isn't the way to go.The Role for Base Themes
Some will sing the praises of Mothership or Tao or their favorite lean base theme of choice, insisting it solves all of the issues I've mentioned. I certainly have no quarrel with using those base themes on projects if you've mastered them and find them useful. It can also be helpful to employ Zen or Omega. It really depends on the specific project. This isn't a post bashing base themes.
My own thinking on the topic, however, has shifted. I've decided to move away from base themes whenever possible. My decision stems from wanting lean code that helps me build fast, mobile-first sites. It also allows me to understand exactly what is happening with the code because I'm the one who wrote it. Ultimately, I think this practice makes me better at my job as a front-end developer, and importantly, I'm also delivering a better product to my clients. I came to this place after spending so much time hacking apart base themes that they were no longer recognizable. It made more sense to just chuck them entirely and start fresh.
Of course, I haven't thrown efficiency considerations aside. I have my own starter theme to make my work easier, and this is what I would advise others who are considering a base theme to do as well. Create your own bag of tricks. If there ends up being things in it that don't fit a particular project, you'll know exactly where they are so that you can easily discard them.
One last tangential thought on this topic - a fantastic development for Drupal 8 would be for core to add no CSS whatsoever, minimal markup and then let themes in contrib add commonly requested bells and whistles. This is a philosophical approach that would be hugely positive for Drupal as a mobile-first approach takes hold as the standard for front-end development.
If you have any comments on this post, you may politely leave them below.
From the webpage:
Primary features listed here, or read the version 2.2 release notes.
- Displays Cayley diagrams, multiplication tables, cycle graphs, and objects with symmetry
- Many common group-theoretic computations can be done visually
- Compare groups and subgroups via morphisms (see illustration below)
- Browsable, searchable group library
- Integrated help system (which you can preview on the web)
- Save and print images at any scale and quality
Are there symmetries in your data?
I first saw this in a tweet by Steven Strogatz.
BTW, Steven also points to this example of using Group Explorer: Cayley diagrams of the first five symmetric groups.
The Next Giant List of Digitised Manuscript Hyperlinks by Sarah J. Biggs.
From the post:
It’s that time of year again, friends – when we inflict our quarterly massive list of manuscript hyperlinks upon an unsuspecting public. As always, this list contains everything that has been digitised up to this point by the Medieval and Earlier Manuscripts department, complete with hyperlinks to each record on our Digitised Manuscripts site. There will be another updated list here on the blog in three months; you can download the current version here: Download BL Medieval and Earlier Digitised Manuscripts Master List 10.04.13. Have fun!
The listing has reached one of my favorites: Yates Thompson MS 36, also known as: Dante Alighieri, Divina commedia. Publication date proposed to be after 1444. (Warning: Do not view with Chrome. Warns of a “redirect loop.” Displays fine with Firefox.)
Great description of the manuscript plus three hundred and ninety-nine (399) images.
But it does seem to just lay there doesn’t it?
It’s a dangerous world out there, now made a little scarier thanks to Heartbleed.
A small coding error in OpenSSL, a massively adopted open-source protocol, the Heartbleed flaw managed to go undetected for two years as it tore security holes across huge swathes of the Internet.
That’s enough to strike fear into the heart of any modern Web-using person—which is practically everyone in the developed world. And yet, most people I’ve spoken to still haven’t changed their passwords or taken other steps to make hackers’ jobs more difficult.
If you’ve also been putting this off, or simply don't know where to start, dedicate a little time this weekend to this checklist of tasks that can help protect you against Heartbleed.Stopping The Bleed
Anxiety has been running high ever since the security flaw was made public on April 7. In less than two weeks since then, legions of Website administrators, app developers, security pros and others have been scrambling to address this mess. Although some companies say they’ve now patched it, plenty still haven’t. It will likely take years before the Heartbleed threat can be considered largely neutralized.
Until then, users find themselves in a weird place. Since the onus is on tech purveyors to lock things down, there’s not much individuals can do—except make it harder for hackers to target them and actually use that data. That’s why experts urge people not to frequent Heartbleed-vulnerable sites, and change their passwords across their various accounts.
This suggestion sounds reasonable; unfortunately, trying to remember every site, service and app you use and manually checking them, one by one, before changing logins is a tedious process. And, in itself, it's prone to human error. After all, there’s bound to be some site or service you forget about.
Sure, you can go to extremes by locking everything down—you can even take yourself totally offline—but realistically, that’s not going to work for most of us. So let’s focus on the simpler things you can do with the biggest security payoff.Step 1: Make A List Of Important Sites And Accounts
Start by corralling your top-priority accounts—anything that touches your financial or medical data, email and messaging accounts, online identities (including social media), or anything else you wouldn’t want strangers to access.
- The sites that come to mind first will likely be your most frequently used applications, which means they're probably important to you in some way, so jot those down.
- Browse through your desktop and phone applications, and call out any apps or accounts that sync your data to the Internet. (Note: Intranets, VPNs and other proprietary cloud services may also be vulnerable, but you’ll want to follow administrators’ guidelines for that. Don’t include those in this list.)
- If you’re an Apple OS X user, look at the apps and sites listed in Keychain, which holds usernames and passwords. The Keychain is located in the Utilities folder within your Applications folder.
- If you use a password manager, take note of those accounts as well. (If you don’t use one, see below.)
- Parse your browser bookmarks, for Web accounts you access directly.
Basically you want to consider any app, Website or service that requires login credentials and goes to, or through, the Internet. Keep in mind that some store passwords and log you in automatically.Step 2: Check Which Apps or Sites Are Vulnerable To Heartbleed See also: 7 Heartbleed Myths Debunked
Now that you've compiled your list of sites and services, you'll need to check which accounts are actually vulnerable to this bug. Then you'll go through and change passwords. It sounds straightforward, but it's not, partially because there’s disagreement about how to actually do this.
Some experts say you should change all your passwords immediately. Emmanuel Schalit, chief executive of password management service Dashland, urged users to quickly change their passwords for all critical accounts—like banks, PayPal and email—and then change them again once those sites actually plugged the holes.
Others—like Rik Ferguson, vice president of security research at Trend Micro—advise holding off on changing passwords for affected sites until they’ve implemented the fix.
Ferguson tweeted that changing one's password “while the vuln[erability] is probably under widespread exploitation isn’t a good suggestion,” adding, "Changing now increases your risk of exposure in the short term as the vuln[erability] is now public."
The latter suggestion appears to be the predominant wisdom, but either way, it's necessary to check each one of your important sites and note which are vulnerable to this bug. CNET offers an ongoing Heartbleed status list for popular sites, but there are other tools that can help:
- Browser users can install extensions like Chromebleed (Chrome) or Heartbleed-Ext (Firefox) or Netcraft (Chrome, Firefox, Opera), to see if sites they’re visiting are affected and get browser notifications.
- Android users can check on their device’s Heartbleed risk using Lookout’s Heartbleed Detector app, or use Bluebox Heartbleed Scanner to evaluate both the operating system and installed applications. There’s also a Heartbleed app for Windows Phone, though it’s simply a URL checker. Apple says iOS is not vulnerable to Heartbleed.
- Check URLs directly with an online Heartbleed checker, like the ones by Filippo Valsorda or LastPass.
For Android users, we may just be scratching the surface. According to Google, most gadgets that run its mobile operating system are safe from Heartbleed exploitation, except those that run Android 4.1.1. But Lookout claims that a few Android 4.2.2 devices could be affected.
A representative from the company, which compiled data from 100,000 of its app users, told me that 5.4% of users running 4.2.2 had the affected version of OpenSSL with Heartbeat—the specific extension that carries the Heartbleed flaw—enabled. These mobile devices could be running custom versions of the Android software, but for peace of mind, you can use Lookout or Bluebox’s mobile apps to check your handset.Step 3: Change Your Passwords
The final step is changing your passwords for every site that’s no longer vulnerable to Heartbleed, especially those were initially at risk but have now patched the hole.
There are three common ways to deal with passwords, but the first two of these are incredibly insecure: Many create the same easy-to-memorize login for every site, or set different passwords and store them in a text file for easy access. But we recommend you keep your passwords diverse and store them all in a password manager.
Here's what you need to bear in mind when changing passwords:
- For optimal security, you want long passwords with random numbers and punctuation.
- Passwords are more secure if there are no actual words in them.
- Vary your passwords for each account. Every single one of them.
- Can't remember them all? Few could. So rely on password managers instead—that's what they're there for. In fact, not only can they store your logins, but they can suggest new ones, too, which would take care of all of the above.
There are plenty of password management apps and services—like LastPass, Dashlane, 1Password, Keeper, Roboform, Lookout and PasswordBox. They're basically highly encrypted password vaults that work across different devices—whether iOS or Android, Windows or Mac. And most of these services feature password generators that can toss out different, hard-to-guess logins for every account. LastPass even has a Heartbleed checker built-in.
Note: If you're a small business owner or running a team, you may need a more robust, collaborative password manager with administrative functions instead. In that case, something like Meldium or OneLogin may be up your alley.Other Considerations
You can change all of your passwords now, or only some, subtracting those services that are still vulnerable. Either way, you’ll still need to stay on top of the Heartbleed status for affected sites, so keep one or more of the tools listed above on hand. You'll also want to keep your desktop and mobile apps updated so you always have the latest security updates.
Finally, if you haven’t done so before, activate multi-factor authentication wherever you can. It’s a secondary security protocol that usually involves sending a code or password to another device, like your smartphone, before allowing account access. On sites that offer it—including many online banking services, and email and social networks like Gmail, Twitter and Facebook—you can typically enable the feature from the settings page after you log in.
Unfortunately, even this extra layer of security isn’t foolproof. Nothing really is, though, short of shutting down our accounts and going totally offline. But even then, our information is often saved online in some way. So even though end users can't fix this hole—it's up to the Web's architects to shore up the leaks in the Internet's foundation—we can do more than just sit idly by. We can and should create more obstacles for the intruders who would exploit it.
I’m hard-pressed to think of an area of technology that has more really good apps then the Organizer, To-Do List, TaskManager space.
Each has its own strength and it’s own philosophy. Recently I have becoming enamored with Trello, The reason, it is visually very appealing and creates a corkboard metaphor which really speaks to my organizational style. It doesn’t hurt that it’s mostly free!
But free or not, this Trello is one organiser worth considering if you were looking to become better organized in a team environment.
Overcome Email Overload, With Steve
Get control of your inbox courtesy of Me (Steve Dotto) and the good folks here at Lifehack. For a limited time you can take my 3 Steps to Inbox Zero course for FREE ($99 value) Click here for more info.
For a limited time, 3 Steps to Inbox Zero is FREE!!!
Please visit Search Engine Land for the full article.
You can’t control how some people will treat you or what they say about you. But you can control how you react to it.
Ever faced people who bother you? I’m sure all of us have faced such people before. It’s okay when we have to face them just once or twice, but there are times when these people emerge in facets of our life where we have to deal with them on an ongoing basis. They can be business associates, fellow colleagues, friends, or even family members and relatives. In such cases, we have to learn how to deal with them. Here are my 9 tips to handle such people:
The post You Can’t Control How Some People Will Treat You Or What They Say About You appeared first on Lifehack.
July is approaching fast, which means that Ghent is getting ready for yet another 10 days of celebrating. Just like last year, we'll release our app to make sure you know your way around. Some events are public already of which one is my top favorite so far: Madensuyu is playing on the Boomtown festival on july 22. You will not regret attending that gig!
Last year, the Android version was only available in one language, namely Dutch. This year, we want try todo a little better and get as many languages supported as possible: I'm thinking of English, Spanish, German, Italian, French to begin with. Another plus would be translating everything to Gentsch, the local dialect from Gent. So, I'm looking for people who are willing to translate the strings which should only take maybe 30 minutes of your time. You'll also be credited on the Google Play store, inside the app and in code. One remark: you can leave the locations as is, there's no value in translating those.
I've uploaded all strings using Google's Translator Toolkit which has a friendly interface hiding away the XML. If you have a google account, send me your e-mail through the contact form or just let me know in case I have your contact details already. If you feel comfortable hand editing XML files directly, you can also download the file underneath and send it back to me.
- Dutch - needs some update
- English - needs revision
Not a translator, but a die-hard coder ?
The code is still free, so you're welcome to hack along on GitHub.AttachmentSize Gentse feesten - translation file (Dutch)12.61 KB Gentse feesten - translation file (English)12.7 KB
From the post:
Ever seen a TEDx talk? They’re pretty great. Here’s one I happen to enjoy, and have used in a couple of sermons. I’ve wondered for a long time, “How in the world do each of these talks end up consistently blowing me away?” So I did some research, and found the TEDx talk guidelines for speakers. Some of the advice was basic – but some of it was unexpected. Much of it, I think, is a welcome wake up call to preachers who are communicating in a 21st century postmodern, post-Christian context. Obviously, some of this doesn’t fit with a preacher’s ethos: but much of it does.
That said, here are 12 things TEDx speakers do that preachers usually don’t:
A great retelling of the guidelines for TEDx speakers!
With the conference season (summer) rapidly approaching, now is the time to take this advice to heart!
Imagine a conference presentation without the filler than everyone in the room already knows (or should to be attending the conference). I keep longing for papers that don’t repeat largely the same introduction as every other paper in the area.
Yes, graphs have nodes/vertices, edges/arcs and you are g-o-i-n-g t-o l-a-b-e-l t-h-e-m.
The advice for TEDx speakers is equally applicable to webcasts and podcasts.
Danny Bickson writes:
I got the following venturebeat article from my colleague Carlos Guestrin.
It seems there is an interesting trend of allowing data scientists to share their work: Imagine if a company’s three highly valued data scientists can happily work together without duplicating each other’s efforts and can easily call up the ingredients and results of each other’s previous work.
That day has come. As the data scientist arms race continues, data scientists might want to join forces. Crazy idea, right? Two San Francisco startups — Domino Data Lab and Sense — have emerged recently with software to let data scientists collaborate on multiple projects. In a way, it’s like code storehouse GitHub for the data science world. A Montreal startup named Plot.ly has been talking about the same themes, but it brings a more social twist. Another startup, Mode Analytics, is building software for data analysts to ask questions of data without duplicating previous efforts. And at least one more mature software vendor, Alpine Data Labs, has been adding features to help many colleagues in a company apply algorithms to code on one central hub.
If you aren’t already registered for GraphLab Conference 2014, notice that Alpine Data Labs, Domino Data Labs, Mode Analytics, Plot.ly, and, Sense will all be at the GraphLab Conference.
Go ahead, register for the GraphLab conference. At the very worst you will learn something. If you socialize a little bit, you will meet some of the brightest graph people on the planet.
Plus, when the history of “sharing” in data science is written, you will have attended one of the early conferences on sharing code for data science. After years of hoarding data (where you now see open data) and beginning to see code sharing, data science is developing a different model.
And you were there to cheer them on!