anon4242

What you want is something akin to Terra: http://terralang.org/

If you haven't used any source control at all, I don't see why svn would be easier to understand than git? Using git will save you from a lot of pain up ahead so I would definitely go for git.

Hehe, seeing this I thought "Cool, this is exactly how Spotify handles separation between the GUI frontend and the backend in the Spotify app" and then I saw the organization name in the URL.. doh!

Actually, __FUNCTION__ won't work as it only expands to the name of the function, not any templates or arguments.

It's actually a pretty clever way to automagically deduce not only names of variables but also of enums :). Too bad it's most likely not maintainable in the long run as compilers probably change what their __PRETTY_FUNCTION__ (or equivalent) macros expand to in new versions.

Hehe, when teaching my 8yr-old programming (in Python) I call (function call) parenthesis a hug to explain that a function "hugs" all arguments to it. She seems to get that :).

Without knowing almost anything about Firefox Send, it does seem that the key is embedded in the link you give to your friends. In that case E2E means that the key is not stored on the server. In order to guarantee that, the link is probably in two parts, one that identifies the file on the server and one is the key. The key part of the link is probably generated on your machine and thus never sent to the server (to prevent it being in any logs or what not). So if Mozilla's servers are compromised the attacker still would not be able to decrypt your files. Of course if the server is compromised the attacker could serve up malicious JS for future uploads.

This is the case with all E2EE tools. You have to trust that they do their crypto correct and that they aren't evil. As Firefox Send is open source you can setup your own server if you don't trust Mozilla, but then again, if you don't trust Mozilla you might want to eyeball their code carefully first...

> In a web app, a single compromised server will compromise all security instantly.

This is only true if the server has access to the keys of your data. E2EE typically means that it doesn't, only you do.

Some ideas can be great in the small even if they won't scale. Not everything needs to be built for massive scale.

There seems to be a conflation of toxic and productive which I don't think is necessarily true. In my case the most toxic coworker I ever had was one who was notoriously unproductive but managed to kiss upwards and kick downwards in ways that made it take a while before management noticed.

I'll give you the benefit of a doubt that you are arguing the general case, but I'm talking about this case specifically. If all you need to do to access the data is to just browse to a specific address, it matters not whether you need to put http or https in front of that address. No need to set up any eavesdropping devices en route. Just point your browser to the address and download the data. Transport security will not protect your data if you have no access control.

So your reasoning goes that if I leave the front door to my home open, it would still be more secure if it had steel bars on the windows?

If I record a phone call between you and me, then put said recording on pastebin or what not, can you honestly blame your phone company or mine?

Still, sending the data unencrypted wasn't so much the issue here as the server was open to anyone.

Not sure it's the right thing(tm) to do but I generally make it "worse" for both of them if they ask me to solve their fights. E.g. if they fight and shout "Mom! Dad!" I'll tell them "Great that you're not playing any more, here are some chores that need doing".

> Other commands like stash, checkout and branch are equally simple

Ok, so they are the simple because you say so? Stash in all but the simplest cases is a sure-fire way to shoot yourself in the foot. Checkout is a weird guy, he does too many different things, and what's up with the double dashes? Super-weird! Also beware that any of your branch names happen to match any of the file names in the repo :O.

> I think where people express confusion over git is that they don’t expect to be interact with revision history

This is one of the things that confuses beginners about git, but it's not a confusion about git cli. You are conflating the criticism of git cli with criticism of git. Git is good, git cli is (notoriously) bad. However, eventually you'll (hopefully) learn the proper incantations and then using git cli will seem simple to you.

Ah, irony. Or maybe you could explain what's intuitive about the number of completely different things that for instance 'git checkout' is used for?

I like git, but the cli is only usable after a dash and a spoonful of aliases.

It may work well to purge the civil service of those not loyal to Trump, but it will also work to purge the civil service of the most competent workers.

[Citation needed]

Git is after all designed for this distributed scenario, so you'd think it would be possible, what about something like:

Setup:

    git add remote gitlab ...
    git add remote github ...

Then whenever you need to sync:

    git fetch --all
    git checkout -b gh --track github/master
    git checkout --track gitlab/master
    git merge/rebase gh
    git push gitlab

Could probably be done shorter but those steps should do it..

The funny thing is that what DuckDuckGo is doing is actually working... By limiting ads to the search words they manage to provide relevant ads (insofar any ads are ever relevant). It turns out that when I search for "office chair" I'm actually not shopping for the Macbook Pro I was looking at a month ago... :O

BLE has support for encrypted communication so should be ok, at least in theory.

So for someone who's looking for a Macbook for iOS app development (mainly simple games in C++), will a Macbook Air suffice?

> You're not going to stop a pro.

The only thing stopping a pro is to have an uninteresting car. My idea is to have a car good enough not to be easily stolen for a joyride but uninteresting enough for a pro.

My thoughts exactly.

I've mostly worked in small companies with tiny engineering teams but I've had a go at some larger companies as well. Personally I thrive in the small companies and wither in the large ones. In the small companies I tend to spend a large part of my day writing code (which I love), meetings are rare and typically to the point. In the big companies I've found it hard to find stuff to do and the meetings are many and repetitive. It seems to me that the bigger companies hire for redundancy. In the largest company I worked for (~3k ppl) I typically received >100 emails/day + dozens of slack channels. In my current job we're 8 ppl and I rarely get more than 1 email/week :)!

Not sure whether legally binding but many of the contracts I've been given as an employee has included at least some paragraph about damages in case my actions as employee hurts the company (e.g. disclosing trade secrets, poaching employees, etc).

I was asked in a Spotify interview to reverse a string as a warm up. When I wrote std::string(s.rbegin(), s.rend()) the interviewers seemed pleasantly surprised.