Merge pull request #796 from jakeherp/read-time

Read time

src/blog/what-open-ai-s-gpt-3-means-for-developer-jobs.mdx

@@ -8,8 +8,6 @@ date: '2020-08-02'
 
 If you have been on Twitter, or anywhere on the internet for that matter, over the last few weeks, you will have come across the cryptic abbreviation "GPT-3", which stands for "Generative Pre-Training (of language models)", version 3. While its predecessors GPT and GPT-2 were far less effective and therefore less impressive, version 3 has caught on in the development world. You might have seen examples, where GPT-3 is trained to generate React components or SQL queries just by giving it text input. Developers fear for their jobs, but should they?
 
-{% twitter 1284807152603820032 %}
-
 While the examples mentioned above are impressive, the reality is, that there is a difference between these presentations and the reality of using an AI algorithm to code complex applications. AI models, such as GPT-3, tend to misrepresent certain user input and might, therefore, go in a completely wrong direction very quickly.
 
 ## Product owners will replace developers with AI

src/pages/blog/[slug].tsx

@@ -19,6 +19,9 @@ export default function BlogPost({ post, mdxSource }: any) {
 		ul: (props: any) => <List {...props} />,
 	};
 
+	const numOfWords = mdxSource.compiledSource.split(' ').length;
+	const readTime = Math.ceil(numOfWords / 250);
+
 	return (
 		<>
 			<SeoHead
@@ -27,6 +30,7 @@ export default function BlogPost({ post, mdxSource }: any) {
 			/>
 			<Container>
 				<Headline>{title}</Headline>
+				<em>{readTime} minute read</em>
 				<MDXRemote {...mdxSource} components={components} />
 				<Flex>
 					<Text>