summaryrefslogtreecommitdiff
path: root/wiki/dev
Commit message (Collapse)AuthorAge
* Syntax highlightingRichard Metzler2018-12-23
| | | | | | | | | | | | | | | | | | | | Also I think Go has the better error handling. Because it is only one and it is supposed to be next to the fallible Operation. Last time I counted there were at least these methods to signal an error in JavaScript: - a return value indicating the error, sometimes as magic number (null or -1) - throw an Exception - an error callback function, which is totally dependent on the framework you use You didn't handle any errors in your JavaScript example, because you aren't forced to. In Java, there are Exceptions, but calling code isn't forced to handle unchecked RuntimeExceptions and Errors. And if you handle Exceptions wrong - and there are so many ways to do this, like swallowing or rethrowing without the root cause, you'll need much time to look into your production issues. Go code is explicit and requires the programmer of the calling code to recognize the possibility something might be slightly wrong in some computer sometime. You're still allowed to ignore this warning by using `_` in `a, _ := fallibleOperationA()`, but it is much better and also cheap if your editor has snippet support to just type `ife`and hit tab and atom is expanding it to: ```go if err != nil { return } ```
* Some notes towards a chat serviceOwen Jacobson2018-03-09
|
* Fix argument typo (thanks, Christophe Junke!)Owen Jacobson2018-02-27
|
* Two trivial typos ("repsect", "disasterous")Ben Zanin2018-02-22
|
* I do not like Go.Owen Jacobson2018-02-21
|
* Add links to recommended papersKit La Touche2017-08-17
|
* papers pleaseOwen Jacobson2017-08-17
|
* A note about recordsPath, care of @TheLarkInnOwen Jacobson2016-07-15
|
* Typo.Owen Jacobson2016-07-15
|
* Some revision to my Webpack primer. I made mistakes!Owen Jacobson2016-07-15
|
* 3,000 words about Webpack.Owen Jacobson2016-06-15
|
* More clarification around secrets & risksOwen Jacobson2016-06-05
|
* Add note on secrets, fix indentation.Kit La Touche2016-06-05
|
* Some thoughts on browser app config.Owen Jacobson2016-06-04
|
* Revert to straight-quote apostrophes for now.Owen Jacobson2015-11-01
|
* Some editorial fixes.Owen Jacobson2015-10-21
|
* The GPL as collective actionOwen Jacobson2015-10-21
|
* Fixup image links for Dokku-based version of site.Owen Jacobson2015-07-17
|
* Backpressure and eviction (thanks, @idcmp!)Owen Jacobson2015-05-25
|
* Observations on buffering.Owen Jacobson2015-05-25
|
* Entry points, with contributions from @aeleitch and @wlonk.Owen Jacobson2015-05-13
|
* Typo fix (thanks, @ashok!)Owen Jacobson2015-04-13
|
* Rumblings about webapp versions.Owen Jacobson2015-01-21
|
* Webapp rambling.Owen Jacobson2015-01-06
|
* Added the catch-all case to falsehoods about shutdown hooks. (Thanks, @idcmp!)Owen Jacobson2014-10-27
|
* Typography.Owen Jacobson2014-10-27
|
* Wrong Things about Shutdown HooksOwen Jacobson2014-10-27
|
* The usual quote-mark fixing.Owen Jacobson2014-10-14
|
* Initial version: what's wrong with jenkins? Lots.Owen Jacobson2014-10-14
|
* Typographic fixes around double quotes.Owen Jacobson2014-05-28
|
* Oh, yeah, mention why this matters.Owen Jacobson2014-03-14
|
* Stop that. Seriously.Owen Jacobson2014-03-14
|
* Some notes on SCM philosophy.Owen Jacobson2013-05-07
|
* Tasks have assignees. Maybe this is implementable?Owen Jacobson2013-03-14
|
* Extended musings on states and speciation with more "why" (thanks, ↵Owen Jacobson2013-03-14
| | | | @jessamynsmith!)
* Extended task tracking remarks a bit.Owen Jacobson2013-03-13
|
* Notes towards bug tracking.Owen Jacobson2013-03-13
|
* Added some notes on how to shot debuggerOwen Jacobson2013-02-15
|
* Wrote out my theory on commit messages.Owen Jacobson2013-02-12
| | | | For context, also threw in my borrowed theory on comments.
*-----. Imported several articles from WordpressOwen Jacobson2013-01-03
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Merging Structural Changes (actual article) * Shared Models Bad (draft) * Twigs (notes) * Liquibase (draft)
| | | | * Imported draft about liquibaseOwen Jacobson2013-01-03
| |_|_|/ |/| | |
| | | * Imported notes about branches/twigsOwen Jacobson2013-01-03
| |_|/ |/| |
| | * Imported draft of single-responsibility articleOwen Jacobson2013-01-03
| |/ |/|
| * Git can merge structural changes, kind ofOwen Jacobson2013-01-03
| |
| * Those scripts have long since vanished.Owen Jacobson2013-01-03
| |
| * "Recently" in 2008. It's 2013 now.Owen Jacobson2013-01-03
| |
| * Imported "Merging Structural Changes" verbatim.Owen Jacobson2013-01-03
|/
* Moved builds.md-specific resources into a dedicated dir.Owen Jacobson2013-01-03
| | | | | This is under /media to avoid conflicts between `.../dev/builds`, the article, and `.../dev/builds/`, the directory.
* Much-delayed editorial fixes to build rant.Owen Jacobson2013-01-03
| | | | | | * The Code Complete link wasn't really relevant, as spotted by a commentor on the original Wordpress version of this article. * The alt text for the pyramid image is less useless.
* Converted build rant to markdown, verbatim.Owen Jacobson2013-01-03