Holy crap, got the call from the recruiter today saying I passed. WTF. I'll be going on site.

They don't expect you to solve all the problems

Seems like pretty good money to me. 110k+ unless my math is really bad.

You should make *way* more as an hourly contractor than as a full time employee. I don't know the formula Dave is referring to but I'm guessing somewhere between 1.5 and 2x as much. Which makes $110k/year pretty bad.

I've never been asked more than 2 coding questions in a phone screen. Maybe they were really testing how strong you were with the 3rd question but didn't hold it against you if you failed it.

The math is off btw there's about 2000 working hours in a year if you take no time off

I assume he was using the 53.50 number and assuming 40h/week, 52 weeks/year which is $111,280. But yeah, you typically get some days off there.

oh thought he was talking about the $45 never mind

what was the third question?

tabs or spaces

I thought you were talking about the $45 / hour. I grew up in Cleveland and I know that $1k / month is crazy high rent, only for a place in the lakeside, and you can buy mansions for $110k in the 'Heights, but in the bay area, $1k / month will get you a bedroom in the bad parts of Oakland, and a long scary walk from the BART.

From what I hear, $45 / hour is what you'd give a fresh face with no experience or functional projects. A DBA is going to be earning well over $45 / hour, plus full time and benefits. Very different worlds, but this disregards the fact that I'm not a DBA by any measure of the imagination. It's funny because they are always willing to scale back the requirements to basically a data engineer, which still, should be more than an ETL person earning said $45 / hour.

Can't say but it was a dp problem. Relatively easy I think, but my mind wasn't framing the problem correctly.

The talk:

There was one "went wrong" moment. I don't know how to hook up Fedora via HDMI. After 20 minutes, I finally got it to work (restart the computer, lol), but my own screen went into "very large" mode and I could only see the top-right quadrant of the screen. The screen on the wall captured everything, but the angle I was standing made it impossible to see.

Everyone telling me that I am crazy for trying to do a live demo was all the encouragement I needed, so I did it. Thanks.

Despite being mostly blind, I did pretty darn good. Got a few laughs at the beginning and I only made a few minor mistakes. The most "duh" moment was accidentally tapping the overwrite mode in emacs, but that was a pretty simple fix and didn't take any time. No one sighed or got irritated since I quickly recovered.

The final part was a Q&A. I only mentally prepared for one question: "why use this and not something else?" Before going in, I thought of a long and ranty reply, but just stuck to a few ideas and basically punted, admitting that I really don't have any convincing arguments one way or the other, and honestly, I think everyone was on the same page and understood the pointless nature of this kind of question, though it was extended and probed for a few minutes longer. No more questions... really?

Well, no. At the end, a bunch of people came up and asked me questions in private. They were all new programmers and were asking things that they clearly wouldn't be comfortable asking in front of an audience. It felt kind of good to answer these simple questions and just be so helpful and enouraging.

Thanks all around. The session ended and the host said to the whole room: "He did a pretty good job there. Doing live coding like that is way harder than he made it look."

ahhhhhh :nerd rage:

someone overrode my code to fix something completely irrelevant, didn't tag me on the PR, didn't test, released it and now it looks like ****

the funny thing is that another team wrote the original UI component, and we thought about re-using theirs, but they're prone to make errors, so we copy/paste their code (almost identical template, but slightly different controller logic) and moved our piece to a totally different part of the repo, of course they somehow manage to change both

i guess it's my fault because my backend code is 95%+ cov but i don't have any for angular grrrr

we're migrating to react now, gonna step up the testing game for sure

Chatting with a potential vendor today (this is for something I manage at work wholly unrelated to programming) and they sent me a link to their sales list. It was hosted on Github and the data was displayed a little annoyingly, so I went to see if I could clone their repo and edit it myself. Went looking through their Javascript and ho-ly ****, it was something like:

If anyone is ever feeling bad about a job search or something, just go read this post again and remind yourself that somewhere, an employed programmer wrote this.

<-- not at all surprised.

It kinda irks me that people like ^^ are the reason Javascript gets such a bad rap. If a million bad programmers flock to Python and start writing **** code should we call Python a bad language too?

You can absolutely write clean JS. Most people just don't care enough to do so.

absolutely. but it would have nothing to do with the million ****ty programmers.

Since Python is the domain of sysadmins, scientists, marketers, and beginners, I'd say Python has the ****ty programmer / non-programmer market cornered. The difference is that none of these people are paid to program full time.

Took new job offer. Way I see it is if I go for a year on contract to hire and I'm not loving it I can probably find another contract no problem. Now to set up an LLC. "Gruepon" obviously.

What, not info.com?

So I'm reading about yarn, and this caught my eye, as we have had to work around similar issues:

However I read this whole thing and I can't figure out how yarn solves this problem. Any idea what I'm missing?

I'm guessing it's in here, particularly the fetching part. Not a great article. Terrible name. Yarn is a crucial component part of Apache Hadoop.

The install process is broken down into three steps:

Resolution: Yarn starts resolving dependencies by making requests to the registry and recursively looking up each dependency.
Fetching: Next, Yarn looks in a global cache directory to see if the package needed has already been downloaded. If it hasn't, Yarn fetches the tarball for the package and places it in the global cache so it can work offline and won't need to download dependencies more than once. Dependencies can also be placed in source control as tarballs for full offline installs.
Linking: Finally, Yarn links everything together by copying all the files needed from the global cache into the local node_modules directory.

On the corp to corp arrangement,

LLC Tax Advantages and other Stuff

I got the impression the global cache was local to that machine/VM - like NPM's cache. I guess if there's a shared global cache that could work. Still though, assuming that is the case - if you have computers you don't want on the internet, it's not that safe to have them connected indirectly (via this global cache, where ever it lives) to a computer that is connected to the internet.

It's long been my biggest complaint with NPM that they don't just write the ability to check multiple caches into the client. IE - check local, if it's not there - go to npmjs.com. I've gone around and around with Forrest Norvell on twitter about it a few times. He pretends not to understand why this would be useful, but then ultimately tries to pitch npm enterprise.

Gee what's simpler - client checks one repo first, if the package isn't there it goes to another repo vs. set up and maintain an internal npm repo/proxy server somewhere that everyone has access to?