lil1729

May be this is the easiest thing people can do?

What are some alternatives to Firefox on GNU/Linux?

I have been working remotely for a while now. These are the things I learned.

- time difference matters. It is better if there is some overlap with at least some people in the team.

- "showing up" (via various communication channels) have more value at one of the places I worked than the actual work.

- I was consistently rated less compared to others because my interactions were only over video, once or twice a week and via chat channels and it could never make up for face-to-face communication. This is highly subjective. At another place, I never had such problems.

- Expect to add a lot of stress in your life (again subjective).

- Pair programming with colleagues over video/google-hangout can be extremely valuable.

- video calls mostly suck, especially if you have low upstream bandwidth (which was the case with me).

- make plans to travel and stay with your colleagues for a week or so, once in a few months.

- "everyone being remote" is better than one or two people alone being remote and the rest in a central office. That way, the company is "set up" for remote working and people take care to put everything online in a wiki etc.. Not so, with a centralized office with only a few people working remotely.

- It is also very easy to get burned out working more hours, especially if the other side is in an overlapping your day. It happened to me many times. This needs fixing at org level and should meet the expectations of everyone.

HTH.

https://ghc.haskell.org/trac/ghc/wiki/Records/OverloadedReco... https://ghc.haskell.org/trac/ghc/wiki/Records/OverloadedReco...

My reasoning was very simple. Nixos makes it easy to install packages on a per user basis. This would mean there is a lot of redundancy if another user also needs the same package. A snapshot/dedup filesystem will easily solve the problem.

Yes, I know it is fixed. But who knows what one runs into!

And this: http://blog.moertel.com/posts/2005-08-22-how-to-change-symli...

* I share the concern of the author on symlinks farm. It is scary! I would like it to be dealt with in the filesystem layer (Plan 9 had a snapshot based filesystem - fossil - years ago). Symlinks have all sorts of weird semantics on different Unix machines.

* Another of my gripe with nixos is that it makes Unix, a single user machine! Sure, packages need not be installed in a user-local way. I may be ignorant of other possibilities here.

* More care for licenses. I still use Debian because they really care for licenses. Last I looked, nixos was in no way close to Debian in terms of documenting the various copyrights and licenses of files pertaining to a package.

Otherwise, Nixos is a great idea and a huge step forward.

British did a lot of nasty killings in India as well, for instance the Jalianwala Bagh: https://en.wikipedia.org/wiki/Jallianwala_Bagh_massacre

I meant to say, generalizations don't always work well. They may have bad engineers. But they have great engineers too. Kent Dybvig and his team who wrote Chez Scheme works for Cisco. There are many others. Jonathan Rosenberg who wrote many Internet RFCs on fundamental protocols that run the Internet voice/video works for Cisco.

Let's not generalize. It hurts people!

1. Make git aware of your signing key

git config user.signingkey "..."

2. Sign the commit

git commit -S ...

That's it.

LWN gets me what I want. It is the most important resource for a linux kernel or in general Free Software enthusiast. Average HN crowd perhaps does not fit into that stereotype.

"Unlike X11, where the graphics primitives were rather low-level and all input event handling involved round-trips to the client, NeWS was advanced enough that simple widgets, such as scroll bars and sliders, could be implemented entirely server-side, only sending high-level state changes to the client, more along the lines of “slider value is now set to 15” than “mouse button 2 released”. Similarly, the client could ask the server to render a widget in a given state, rather than repeatedly transmitting sequences of graphics primitives."

There is no cloud, only other person's computers.

Not sure if these can be applied to digital circuits, perhaps not very easily, since a lot of components are SMD these days, at least in the high speed digital domain.