opcenter

> At the moment, many people want to vaccinate their kids, but I doubt it will still be the case in a few years when the panic induced by the pandemic has subsided and people have realized that SARS-CoV-2 is harmless to children.

Except, SARS-CoV-2 is not harmless to children. I think it will become a common seasonal vaccine for kids, just like the flu vaccine.

The worst part is that you end up breaking your fingers when you want to angry type a rant about the keyboard. :)

I picked up a bluetooth mechanical keyboard that I just carry around with me and don't use the laptop's actual keyboard at all.

I took a quick look at the list of commands and they looked so similar to the primary git commands I use that it seemed like a waste. Better to just learn how to use git.

I think the basic idea is sound. If all you're after is learning to program and running little toy programs, then web based REPLs are a great choice.

My primary development environment is vim combined with CLI commands (and some wrapping with vim plugins to simplify the workflow). However, when I want to play around with something in Go to figure out how it works I will often go to The Go Playground (https://play.golang.org/) and play around there.

However, as soon as I'm done (and maybe shared my findings with a peer, which I can't do as easily with my local vim + CLI environment) I'm back to my regular development environment because very little that I work on is trivial enough to stay in Go Playground.

All that said, I've seen plenty of developers who seem to get by sticking to the basic feature level of Notepad. Whatever works for you.

It sounds like they don't have enough incentive to stay? I know some others have mentioned financial incentive, but really enjoying the work you're doing and the people you work with may be even more important.

I completely agree with that when I'm using the laptop unplugged, especially if it's on my lap and I want to get maximum battery life.

However, if I'm sitting at a desk where it's plugged in I would like to get as much performance out of it as I can.

Very cool read and a lot of your happy discoveries are similar to reasons why I like coding in Go, especially your "Less Language Feature ‘Anxiety’" section. No guessing about how to do something, there's generally only one way to do something.

So true. Often technical debt is intentionally taken on as a calculated risk to get to market faster with the intention of fixing it later. Fixing it later rarely happens though. In my experience it either ends up being someone else's problem or you just live with it.

I think the problem is that there's a perception that a phone call is an interrupt event. Because you have a person on the phone waiting for you to answer, you have to (or should) answer the call.

So, if the matter is important then a phone call is completely appropriate. But if it's just a call to say "hey, how's it going?" then perhaps a text message or email is a better choice with a "let me know when it's a good time to call" added in so you can have a normal voice conversation without either party being interrupted.

I've had a similar experience with the spam calls. I don't get quite as many per day, but ~90% of the calls I receive are spam. I just don't answer my phone anymore unless it's my wife, my mom, or one of my brothers. I direct all other calls to voicemail after grumbling about being interrupted.

I haven't found a good solution for auto directing spam calls to voicemail beyond using Do Not Disturb from 8 pm to 7 am.

I had to read the post twice before I really got what she was saying. I think the distinction I would make is that while there are many more use cases that you can apply to Containers that may not apply to Jails, Zones, or VMs the most common use case of "run an app inside a pre-built environment" applies to all of them. Since I believe most users (or potential users) of Containers are only looking at that use case, it's harder to see the differences between the different technologies.

My only hope is that anyone in a position of making a decision on which technology to use can at least explain at a high level the difference between a Container and a VM.

Looks like that has 8 cores? I would imagine it would make a huge difference depending on other loads on the system. I gave it a try on my file server at home that has an AMD E-350 processor with 2 cores and it shaved off a good 42% of the total time:

  > time gzip -v xubuntu-16.04-desktop-amd64.iso 
  xubuntu-16.04-desktop-amd64.iso:	  1.5% -- replaced with xubuntu-16.04-desktop-amd64.iso.gz
  gzip -v xubuntu-16.04-desktop-amd64.iso  119.07s user 4.66s system 98% cpu 2:05.22 total

  > time pigz -v xubuntu-16.04-desktop-amd64.iso           
  xubuntu-16.04-desktop-amd64.iso to xubuntu-16.04-desktop-amd64.iso.gz 
  pigz -v xubuntu-16.04-desktop-amd64.iso  128.19s user 6.64s system 184% cpu 1:12.97 total

My general rule is that I will stay with the same job for at least 1 year. Part of that is to not look like I'm job hopping, but mostly it's because it generally takes me around 6 months to fully acclimate to the environment and another 6 months to get deep enough into development to figure out if it's somewhere I want to stay.

Of course that timing changes depending on the product and company. If you're working on a well established product at a medium to large company it may take longer to do much real development (beyond bug fixing and paper shuffling), so it may take longer to figure out if you want to stay longer. However, at a startup, you'll probably be dropped right into the fire on the first day, so you may be able to determine that more quickly.

When I've looked at resumes, anything less than a year at a job usually raises a flag. Unless there are a lot of jobs on your resume like that, it's not a negative thing, but I would absolutely ask about it during an interview.

>If you say "This is something I built in my free time", or "This is something I built while I was learning Backbone" (and keep you tone enthusiastic, not apologetic), then people will understand the context in which they should be judging what they see. If they're smart, they'll realize that seeing what you can do when you don't have much time, or when you're on unfamiliar ground, is at least as valuable as seeing what you can do under ideal conditions. If they're not smart, do you want to work for them?

That's a good point and it's what I've been following so far. "Here's a project I built in my free time because I wanted to brush up on my Python skills, and in the process I also learned a lot about Flask, MongoDB, HTML5, CSS, and JavaScript."

> That's hard too. It might help if you can come armed with some benefits of releasing something as open source, like the fact that other people will be able to find and fix bugs for your employer, which is basically free labor.

Also a good point. I'll have to give that a try.

I fall into the "developer 1" category myself. I only recently started doing side projects in my own time (and publishing them on github), almost entirely because I was starting to run into walls job searching without a "portfolio." Unfortunately, this means that what potential employers are seeing is stuff that I've done in my almost non-existent free time, so it's generally unfinished, unpolished projects that had a really simple goal or were for learning a new language/framework. So, it's not necessarily a good indicator of what I produce when I can focus full time on a project.

It sucks that I am "punished" because all of my actual work has been for companies that aren't interested in sharing their products with the community. I've even tried a few times to get tools I've created released as open source, but the general response I get is, "uh, why?" I can understand that the companies see no value in it and in fact may cost them money if there end up being licensing or other legal issues.

Should have named it red pill. :)

Seriously though, I was more excited when I thought it was about running Linux inside the browser. Personally, I have no interest in installing an extra VM on my system just to make your development easier.

Very interesting background and well written. My own schooling was more straightforward. I went through K-12 normally in (thankfully good) public schools in NJ and then got my BS in computer science at a relatively normal 4 year university. And I have to agree with you that none of that taught or encouraged self motivation. I always felt like I was just going through the motions to finish school and get to the real world.

Work after college didn't help either. All of the jobs I've had so far (going on 12 years now) have spoon fed me work to do and only my most recent job has given me any flexibility to be creative and solve problems that are beyond the scraps of work they give me.

Getting a taste of building something that I see a need for that wasn't just assigned to me has finally started me towards feeling some motivation to do my own projects on my own time and it feels really good. Over time I hope that I can expand this to my actual job and other parts of my life. I'm just a little sad that its taken me until my mid-30s to get this, so I'm glad to see you've figured it out as early as you have and I hope to help my daughter learn it early on. :)

That research lines up pretty well with my own experience in college. It haunted me until my 3rd year when I was so bogged down with advanced projects that I just couldn't keep procrastinating because I was only barely getting the minimum done I needed to in the last hours I had before the projects were due.

Professionally, I've learned my lesson and while I've had some moments of procrastination (especially for tasks that I have little to no motivation for), I tend to work more steadily than I did in those first few years of college and I rarely run up against a deadline (soft or hard).

However, I've worked with plenty of software developers who wait until the last perceived moment and work crazy hours to try to meet the deadline. I'm not sure what they would do if they didn't have that deadline. I suppose they would either get fired for lack of productivity or just be productive enough when nudged to keep their jobs.

My boss is pretty cool about this. He asks for estimates on tasks for resource management purposes, but he assumes the estimates are wrong out of the gate and we adjust as the project progresses. So, I agree that focusing on an arbitrary deadline is foolish, but drawing a line in the sand can help keep people on task.