Swift Playgrounds Reviews

1. Nathan

   over 1 year ago
   Terrible online training course

   The lowest available rating score is 1, but if there were a zero, I would rate this program a zero. There are no pros to this programming course. The lessons are so brief that I cannot understand them. Before I gave up for good on this programming course, I was writing tons of messages to people on Youtube asking them to explain things to me, and I hated the constant hassle of having to write online messages asking for explanations for the simplest of things that the lessons did not explain. This programming course is NOT a do-it-yourself training course by any means --- and it should not be used by schoolteachers as student homework assignments, as I recently advised a 13-year-old who was having trouble with the lessons and nothing was being helpful to him. This training course should be accompanied not by brief and intelligible on-screen lessons, but it should be accompanied by a detailed high school-style textbook complete with images. By the way, I have Asperger's syndrome, I have all kinds of problems with learning and with executing tasks, and I cannot participate in gainful employment in ANY profession for this reason.

hub Reviews

Swift Playgrounds mentions (0)

hub mentions (4)

• GitHub Discussion about the recent feed changes becomes 3rd most upvoted ever

  Use hub here via CLI and forget the gui https://hub.github.com/. - Source: Hacker News / 10 months ago

• Pull request Best Practices

  Try automating the PR process as much as possible. Make use of tools like hub CLI for speeding up the pull request process. Code quality tools can help you automate the due diligence for coding standards and conventions, and test automation tools can assist in bug discovery, and identifying security vulnerabilities. - Source: dev.to / about 1 year ago

• [Media] I made a Rust CLI game that tests how fast you can guess the language of a code block!

  Parse_git_branch() { # Speed up opening up a new terminal tab by not # checking `$HOME` ...which can't be a repo anyway # # For the heck of it, micro-optimize this too: # time (repeat 1000000 { [ "$PWD" = "$HOME" ] } ) == ~4.2s # time (repeat 1000000 { [[ "$PWD" == "$HOME" ]] } ) == ~1.4s [[ "$PWD" == "$HOME" ]] && return # Fastest known way to check the current branch name ... Source: almost 2 years ago

• I have 20 repositories, is there any way I can create a report showing how many open issues in each?

  You can always query via github api or use the hub client (from their home page https://hub.github.com/). Source: over 2 years ago