interatx

We just took it as a mentorship exercise. Couple of gals in the group were really fast learners and didn't need as much help, so we know some eventual new-hires who sort of know our system and way of doing things. Also, their questions were often very simple but piercing.

In my previous role, we had few Junior Devs - Teens who are just about to go to college get to experience working on a professional project and seeing if they like software development at a big (FAANG) co. We didn't treat them as interns because the expectation was they did not know anything about software development.

We pair program with new hires on simpler tasks and gradually build them up. Sounds very similar.

Thanks

Is cleaning the chimney and base difficult?

I see following message

"Sorry, for right now is disabled, but will be fixed very soon!"

Is presence of air / atmosphere essential to generate a drag?

Maybe I missed in the article but how does a browser block cryptomining scripts? Same goes for fingerprints.

As someone who helps teams with security, please don't take dependencies that haven't been reviewed. If you speed is more critical for you, do not expect your software to be secure and __ALWAYS__ have a incident response plan. It should have a way of informing dev teams, management & customers about what happened, what is being done and how soon.

It's not always a choice. I'm in currently Canada where the term "Engineer" is protected https://en.wikipedia.org/wiki/Software_engineer#Canada. So I'm a developer here.

I stopped looking at my keyboard. I was slow initially but ever so slowly became faster. I too would recommend typeracer[1] as a fun way to speed things up.

[1]: http://play.typeracer.com

I've probably abused it too much but its shocking how much it load it can bare.

* Ebook Server

* Ad Block via DNS

* Router (needed me to get an expensive wifi receiver) over VPN

* Mini build system to publish my blog

* Auto-backs up my NAS box to S3 / Glacier (and then test-restore the latest backup) every month

* Auto-emails me based on a wide variety cron-jobs that check the weather, stock market, rss feeds, etc

* Grabs by RSS feeds and bookmarks

* Offline cache for some stuff

* Downloads videos for later reference

* Automatically texts me when I've not written anything worthwhile (in code or blog) for a while

[edit]

* Using it to teach python / basic programming

This doesn't seem to answer all the questions.

I don't have any physical books on my desk[1]. Most of the stuff I usually need is online and takes less time than thumbing through books & indexes.

[1] I think this is most likely situation but wasn't sure if more would answer this.

> Trying to get a sense of what it would be like to live there

The past few times I went for an interview to a new location, I first went to a meetup / group. Asked folks (who have lived and have no stakes in your interview) what they like and don't like. Also, walked few blocks around interview spot in the evening and morning for as long as I could to get a better feel of the area.

apologies. I don't watch the news and had no context.

Oh this is sweet.

My dumb UX feedback (just a user, not a UX expert)

* I expected the hover not hide (or do something) I click on the button

* Considered automatically turning off hiding for accesible devices. https://www.w3.org/TR/aria-in-html/ for reference.

Wouldn't this be covered by #9 ?

I'm currently 50 / 50. Here's what I've had to do to get work done in office :

* Headphones when I need to focus. Even a random noise app is good enough.

* Be patient with those who interrupt unless you have a deadline. They don't know that you're still adjusting.

* Go for coffee / walks with your co-workers. Get to know them and they'll get to know you (and your preferences of working through slack/hangouts)

* Plan for a slight drop in productivity and slight increase in communication

That's what I use on firefox. Works great most of the time.

I do two things

* Log anything and everything that feels like it needs to be done. You can't always add every bit of info but everytime logging something new, I do as much as time allows me to.

* Have regular meetings (every two weeks on a wednesday seems to be working great so far) with the whole team to talk about issues that already exist and the new ones that came.

The team can together decide what's worth fixing, help you understand what's not (at least for now).

I've learned everything the hard way so I'm not sure if this is accurate but I believe this is process is also called as backlog management in the agile world.

> it's a perfect springboard to all the essential topics in software engineering.

Indeed. If anyone is looking to start a new blog and doesn't know where to start, these listicle gives you plenty of ammo. You can just pick one and dive deeper and deeper to become a SME

The site looks good, clean and does a fair job however there's a ton you can add on (which may break its minimalness) like checking how many users are complaining about the side on twitter and maybe allow manual feedback.

Also, if you plan on building this further, get some tests in that package.

I think voice dictation talks to the microsoft home (and has been disabled for my company's one note). At this point my salary is just enough to compensate for a surface pro or surface book to take notes. I think one note + surface pro + surface pen might not be a bad option.

The second link doesn't work but I was able to visit https://github.com/twostairs/paperwork. Looks interesting, definitely will give it a try. Thanks!

I work with someone who stutters here and there. He is very upfront about it. I have not cared about it ever since but it did give help me figure out how to have better conversations with him.