Building Slerk with Brennan

When I attended Startup Slam with some of the PERL team, one of the sessions I attended was “From Zero to Slack in 30 Minutes.” In this session, Brennan and I attempted to build a rip off to Slack, Slerk. We were learning about using React, a JavaScript library that supposedly does really cool things. I wouldn’t know, because I couldn’t get it working.

Here is what Brennan and I did do;

  • Open the MetaLab readme, which contains the instructions for later.
  • Get confused.
  • Pretend to be invisible for when the MetaLab guy turned up to ask if we were doing okay.
  • <invisibility.exe has failed to launch. Would you like to report the error to Microsoft?>
  • When MetaLab dude turned up, he was actually really helpful. He got us started on the process.
  • Create GitHub account.
  • Fork repo and attempt to download it via GitBash.
  • Authentication failed.
  • Log into GitHub app.
  • Attempt to download via GitBash
  • Authentication failed.
  • Stop using GitBash, that wasn’t the correct program.
  • Try again with GitCMD.
  • Success!
  • Oh, someone is done the entire thing already. Turns out, Brennan and I should never be engineers.
  • Run “npm install,” as advised by ReadMe.
  • Misspell “npm.”
  • Endure 20 minutes of laughter from Brennan on misspelling three letters.
  • Actually run “npm install.”
  • This apparently installs all the relevant and required files, which the downloaded repo somehow has listed and has instructed GitCMD to find, download, and install.
  • Green text on screen, which I don’t understand. But green probably means good.
  • Right?
  • Hopefully. Next, we’re to use the command “npm run windev” to start our localhost server.
  • Try not to misspell “npm” again.
  • Fail.
  • Try again, get more green text. It seems we’re live!
  • Go to 127:0:0:1:8080 (or 0:0:0:0:0:0:0:1 for you IPv6 ers!)
  • Hooray! We’re live on Slerk.
  • Except some important features are missing. It seems we’re supposed to fix this.
  • Uh oh, here comes MetaLab dude again. He’ll see our incompetence.
  • Win+R>invisibility.exe>enter
  • <Your PC ran into a problem and needs to restart. We’re just collecting some error info, and then we’ll restart for you (3% complete)>
  • MetaLab dude is, as always, very helpful and not at all judgemental.
  • We’re instructed to change the files that we downloaded from this, with the [message] just being placeholder,
class MyHeader extends Component {
 // Declare what properties your component accepts. static propTypes = { message: PropTypes.string.isRequired } // Use those properties to create a view. render() { return <div>[Message]</div>; 
}
}
  • To do this, with the specific React code (written in the weird {this.props.message} format, as so:
class MyHeader extends Component { // Declare what properties your component accepts. static propTypes = { message: PropTypes.string.isRequired } // Use those properties to create a view. render() { return <div>{this.props.message}</div>; } }
  • Supposedly, that’ll work. It’s supposed to act as like php, and pull the date requested by the {this.props.message} from an external library.
  • Reload localhost to see the changes.
  • *http://localhost:8080 is not available.*
  • I don’t even get a dinosaur to play with.
  • Roll back to untampered file, restart server within GitCMD.
  • Slerk loads.
  • Make a change again.
  • *http://localhost:8080 is not available.*
  • Still no dinosaur.
  • Try again a couple more times.
  • Nothing.
  • Oh, the session is just about to end. Might as well chat with Brennan until it’s over.
  • Alt+F4.

TL;DR:

React is cool. Don’t know how to use it.

GitCMD is cool. Can’t type properly.

Brennan is cool. No errors here.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.