daigoba66

I miss Rdio.

This is solved with perfect forward secrecy: https://en.m.wikipedia.org/wiki/Forward_secrecy

A lot of it depends on the particulars of your database system. But there are certainly tools/solutions that exist, and essentially they all boil down to the same pattern: migration scripts should be executed exactly once in order. How this is done varies.

I do a lot in the .NET/SQL Server world, and my tool of choice is one that I wrote: http://josephdaigle.me/2016/04/03/introducing-horton.html. Conceptually, what this tool does could work for any RDBMS.

I wonder where the tipping is at which it's more economical to own/lease your infrastructure instead of AWS/Azure/etc.?

The company is certainly large enough to have their own infrastructure team.

But granted, migrating an entire system that makes extensive use of the AWS ecosystem is anything but trivial.

honest question: why don't they have push access?

I think, based reading comments and articles from various sources, it's all because of GitHub pull requests. A lot of people seem to rather a pull request be represented as a single commit.

But I'm in your camp: I work with teams using git (and GitHub as a central repository), and a non-linear history has literally never been an issue. Even ugly graphs 7-10 histories wide aren't an issue. We also don't do pull requests (because we would we?).

We don't have a hard time with code reviews just using GitHub's commit history or even Gitk. In fact merge-commits often sometimes useful as markers of when the developer integrated his/her changes.

Admittedly, I'll occasionally do a rebase of upstream changes before I push if I know the change I made was small an isolated - but I certainly don't encourage other developers to do it.

Team members can also work in their own private branches that are pushed to a single repository - that's usually sufficient as a "backup".

I bet this is also a step towards having a proper SSH server running on Windows.

That's what Update 2 brings: "You can now initialize the C# Interactive Window with a project's context, allowing immediate access to types inside that project."

It's actually been there since Update 1.

E911 service is more reliable with a land line, even if it's VoIP, since the location is fixed. Some recommend having a line just for that.

> There’s no “document” version of an app that guesses what age your dog is. I mean, what would that even look like?

I guess the author doesn't realize that code can live on a server. And the answer to his query can simply be a "document".

Edit: I did not catch that the article is supposed to be a joke. If that's true... I suppose it's not very funny.

I'm a consultant; this is good advise.

It's not laziness or apathy. It's just that we're only paid to do a task.

"If you build it, they will come." Except they won't.

It seems to me that, unless your product is a platform, you probably shouldn't publish a public API until someone requests it as a feature. And you should charge for it, especially if your hosting the API endpoint. Turn it into direct revenue to support the development and maintence of those API features.

Amazon SES doesn't require domain verification unless you want to be able to send from arbitrary email addresses for that domain. If you have a known set of senders, you can verify just those email addresses (which works the usual way: email is sent and you click a link).

What Amazon SES might lack in terms of fancy features, it probably makes up for in pricing and stability. We've been using it for over four years and haven't experienced a single problem in that time.

> What I don't like about postgres is that it's really hard to have a decent replication / failover setup manually.

This is one reason I personally have a hard time moving away from MSSQL (despite the obscene licensing). Clustering, replication, and failover of MSSQL on Windows is really quite powerful. Though not necessarily cheap or easy to setup and troubleshoot, it is wonderful when it works.

In the past I've used Dell Latitude E54xx. It's essentially the same as a Latitude T series (size, specs, and price). And fairly equalivant to a 13" MacBook Pro.

I loved that machine.

Now at work I'm stuck with a Latitude W series. While certainly powerful, it barely qualifies as portable. I hate it.

I'm considering getting a 13" MacBook Pro, for myself, whenever they announce an upgraded model this year.

I wrote a bit about it here: http://josephdaigle.me/2015/12/03/search-for-ultimate-dev-la...

SQL Server ships with almost it's own OS implementation, aptly named SQLOS. If I had to guess, the interface between SQLOS and Windows is relatively thin (and just IO, Threads, and Memory Management).

There are a lot of other bits, such as Integrated Security Security, Windows Perf Counters, Windows Event Log, that are probably stripped out.

But I also suspect that that the Linux implementation is based on the implementation that they use for Azure SQL Databases.

> It will never happen.

Some people probably said that about the .NET framework. Now almost all of it (the new stuff anyway, and minus Visual Studio) is fully open source.

To be pedantic, HIPAA was signed into law in 1996. Obama obviously had nothing to do with that. Technically the HITECH act was signed into law by Obama, in Feb 2009. But that was only a few weeks after he took office.

The Affortable Care Act is largely thanks to Obama. And it did add new regulations related to HIPAA and HITECH. But the core principals that you mentioned were already tehre.

> maybe you've got too many and the high volume posters drown out the good signal from the low volume posters (that's where I am at, and don't know how quite to fix it...)

Unfollow. Seriously, that's the best way to decrease noise. Yeah, perhaps they do occasionally tweet something interesting. But if 50%+ is just noise, it's hardly worth it. I'll look for their content elsewhere.

Ditto. I turned off virtually all notifications on my phone. Only phone calls and text messages get through (which for me is quite rare).

I realized that almost nothing on my phone is important enough to interrupt me whenever.

Lost power. Took a while to get the servers cleanly rebooted.

Well, technically you could setup internal only email servers and addresses. In fact, it might even make sense for some companies to go to a whitelist-only approach for most employees' addresses. Unsolicited content could filter through a single mailbox.

Works as advertised.

Coming from pretty heavy background in MSSQL internals, this article is really great.

I keep telling myself that I need to invest time into learning PostreSQL as a (far less expensive) alternative to MSSQL for some use cases.

> Perhaps Kanban is better suited towards long-lived product development than Scrum.

This is the key take-away. And in my experience this is absolutely true.

On the other hand, working now as a consultant where I am frequently on shorter-term projects with a definitive "end" for the engagement, the time-boxed sprint approach (or "Scrum") actually seems to work well.

Scrum might work for individual "projects". It does not scale or coalesce well with long-term development and maintenance.

> Perhaps there is indeed a natural progression of engineering teams adopting Scrum, then moving to Kanban.

This also mirrors my experience.

It's a never ending battle. They never go away completely.

All three major commercial OS vendors: Microsoft, Apple, and Google. MS and Apple push it not only for their mobile OS, but for desktop as well.

Microsoft is pushing it now with their development tooling (e.g. Visual Studio). First, it was "sign in" to synchronize your settings across instances. Now they're encouraging monthly subscription based licensing, which requires you to be "signed in", instead of the traditional perceptual license.