canadev

An interesting article.

Something interesting maybe none or few you will likely experience: Alcoholics Anonymous, Narcotics Anonymous, Cocaine Anonymous meetings, presumably any 12-step meeting.

Say what you will about the 12 steps, and the belief of god that is associated with them. Feel free to disagree with the dogma. As a member I openly do that from time to time.

The real beauty of these meetings is that when someone speaks, they are left to speak completely uninterrupted. (Some groups use a timer and people generally wrap it up when the timer goes off.) Speaking about your experience during a meeting is called “sharing” and it is fucking magical. It’s helped me learn to listen, it’s helped me to speak extemporaneously on things that matter to me deeply, it’s taught me patience as an object lesson. You may not agree with what the other person is saying - there is no rule that you have to, and as might be expected it is not at all an infrequent thing that you hear absolute nonsense or worse. But there are also messages of beauty, there is often identification, there is definitely learning, and there is freedom, and there is genuine respect.

I believe there is some significant power in the 12 steps: confession of harms caused, attempts at restitution where at all appropriate, and learning to take responsibility for one’s actions. I do not believe in an all powerful and loving god because there is simply too much needless suffering in the world for me to agree with it. Occasionally I share about this but I try not to harp on it.

But the real beauty of a 12 step meeting is in the sharing, in my opinion…

Lots of development practices come back again. E.g. techniques for optimizing code for computers sometimes make a resurgence for mobile phones a decade later.

I suppose that is likely true. I just put myself in the poster's situation and started breathing real shallow, haha.

This is a good endorsement!

It's kind of crazy how hard it was for him to get out of there though; I would have expected his flatmate to take care of it straight away.

Rather than a tool like Copilot, which does look very interesting, I'd be curious to see the effect of using evergreen (self-updating) off-the-shelf free open-source components.

Imagine if you get get an app that uses `http-rest-api` and `http-www-crud` with `http-www-multifactor` and `http-rest-api-license-key` and you could automatically be using the latest rest API, the latest CRUD framework, the latest multifactor/whatever framework (which you'd probably pin to some standard like YubiKey so user tokens don't get invalidated regularly). The actual reference implementation could be done in pseudocode even, and ported to many languages (ok this is getting too meta). You could throw together a professional quality application in a few lines of package management. And if someone finds a bug in the code, it gets updated, and next time a release is cut you'll pull it down automatically and deploys itself.

Yeah! I've uh, ... never copied a bit of code into my repo verbatim, right?

yeah right. I wish.

(Not saying every dev does this)

have you a link handy?

Sometimes coding is hard in and of itself.

I agree, and I'm glad I don't work at a place where coding is considered easy work.

This book looks interesting. I'd like some advice on whether it will be useful for me.

I've been a professional dev for over ten years and I have a CompSci degree from a respected university. I'm getting paid principal engineering salary for a moderate sized city in the U.S. and I work remotely from Canada in a fairly cheap cost-of-living city at a small company (far from Silicon Valley salary, but pretty damn high for here).

Do you think this book will be useful to me? I want to maintain my career as a developer and grow in skill and salary. I have started blogging about a year ago and I do infrequently but I think my posts are decent. I also am taking the time to learn some stuff like ML and am constantly trying to improve my skills with stuff like PostgreSQL and Go.

After reading this article I was all set to look into the ReMarkable as a big e-reader. Then I read this thread and I'm glad that I don't!

I have no use for writing in a tablet. Can anyone recommend a big e-reader suitable for textbooks? I'd like a 13" Kindle or something...

I found it: https://github.com/firefly-iii/firefly-iii/issues/2259

demo@firefly / demo

I'd strongly suggest putting that on the demo page itself.

Thanks for the link. What's the username and password for the demo site?

personally, I feel like rm -f is dangerous, and never would recommend using it.

Interesting note about Lambda Labs, all of the press links on https://lambdalabs.com/?ref=blog are about a ~"privacy violating Google Glass app" that recognizes faces and geotags photos of them.

I don't see why they choose to promote that link now.

We definitely weren't deliberately executing commands in parallel and I think it's pretty rare that we have network issues.

Modules in 1.11 have some rough edges. Internally we have written a merge driver which is imperfect for handling version conflicts, and a couple of my coworkers keep having to delete $GOPATH/pkg . I was hoping these would be addressed in this release but it doesn't look like they are.

it's like getting your kids vaccinated

Can someone put this in lay terms for a casual postgresql user?

This is a tangent but they link to a serverless deployment service where you upload your code as a function and they execute it. Pretty interesting.

Another solution is to check them in as git Large File Storage files.

https://git-lfs.github.com/

I think the answer is everything in your standard library plus some of the stuff you would use 3rd party dependencies for in your own project.

Maybe standard libraries need to get bigger for JS.

> It feels like it has a small attack surface, yet we use over 1700 packages. We only have 49 direct dependencies, so the vast majority of these are dependencies of dependencies of dependencies etc etc. The web app itself doesn't use a lot of third party code, so most of these packages are part of the build system.

Wow. Small attack surface with 1700 dependencies. What a hard concept to swallow.

Just in case you don't know about this feature that scrolls the top of the screen down the screen: http://www.cnet.com/how-to/how-to-use-reachability-on-iphone...

that was neat

Thanks for the tip about the clean install.

And I totally hear you about the way the phone feels. Every time I got a new case, I would leave it naked for a few hours, just -[fondling]-touching and admiring the damn thing.

Ah. I totally missed that.

Saw this phone on reddit earlier.

A few weeks ago, after an upgrade to iOS 8, I became unable to connect to wifi on my iPhone 4S and the speed of the OS became pretty bad, after it had been perfectly responsive since I first got it nearly 3 years ago.

Combine this with the fact that my expensive purchased-for-durability phone case, the third in the phone's lifetime, was starting to crack, and I started looking at other phones.

My contract is up in a couple of months. I went to a store and looked at the Samsung Galaxy Note 4 and the iPhone 6.

I found the Note 4 intriguing because I've been occasionally following John Carmack's discussions about the Gear VR (Oculus Rift that connects to the phone) and I thought it was coming out in a consumer version, but it looks like they are still labeling it as a developer kit, which makes me think there must be a reason for that (i.e. it's not really ready for prime time). Also, the phone is just massively huge, and I don't want to buy it, especially since given my way of doing things I'd end up buying some horribly large case on top of it.

Then I looked at the iPhone 6. First of all I do think it's too big in terms of screen size -- though I do like the thickness and weight of it quite a bit. But the base model is 16GB, and getting either a 16GB or a 64GB on contract was $200+ or $375+ respectively. I thought about it and almost broke down and bought a 128GB model outright for over $1000. In the end, I just couldn't justify it.

I think it's time for me to go back to sending SMSs on the telephone keypad. And time for me to stop getting warnings that my damn phone is not backing up (no wifi and me not plugging it in), time for me to stop worrying that the phone will die if I forget to charge it for just one evening, and time for me to stop buying expensive, crappy cases.

I really want this phone. And if I don't get it, I'll probably get something that is just like it.

TL;DR: I'm a fan.