Command+option+shift+4 then press the space bar to take a screenshot of a single window (shadow included).
1,087 karma · joined March 13, 2013
HN@DUNCANREGAN.COM
I don’t know about you, but I’m not running flash like it’s the early 2000s.
I try not to profess in mixed company that young designers should know the history of the web (it’s so young after all!), lest I be pegged an old man yelling at clouds. However, there was a time when there was a really interesting intersection of print designers coming to work on the nascent web, asking for the moon, and web developers teasing out compromises because the platform was so limited. Now that the platform is so capable that it could accomplish those designs, we don’t have designers capable of imagining it.
I’d love for a designer to ask me to do something different for a change of pace. There have been many neat APIs that have slowly made their way to CSS over the years sitting unused.
Children don’t need this; they are so much more creative than an AI (and the adults that trained the AI), and their creativity is fueled by boredom.
Or when the email service is overloaded and the magic link takes more than 30 minutes to arrive and by the time you open it, it has expired?
Also, we haven’t given pitchers a chance to adapt. Perhaps pitching outside (now a thinner part of the bat) will take the force out of the hit leading to softer contact.
And if the season proves that these bats are indeed juicier than others? Probably MLB will let it lie. Offense is down enough already and all of the recent rules changes are intended to support offense.
Anecdotally, I wear a wool coat from Filson that is nearly 20 years old. Halfway through its life they reconstructed the fraying cuffs for free.
0: https://www.filson.com/products/chambray-cpo-shirt-rinsed-in...
My “theory of layout” is that no element should have any styling that relates to its relationship with other elements. Gap is very useful for establishing spacing.
Sadly, out of 100s of people, I’ve probably only gotten an interesting response a handful of times. Mostly people say some well known tech from the job description.
I never held that against anyone, but the people who had an interest in something were more fun to work with.
Take maximum subarray problem, which can be optimally solved with Kadane's algorithm. If you don't know that, you are looking at the problem as Professor Kadane once did. I can't say for sure, but I suspect it took him longer than 30-45 minutes to come up with his solution, and I also imagine he didn't spend the whole time blabbering about his thought process.
I often see comments like: this person had this huge storied resume but couldn't code their way out of a paper bag. Now having been that engineer stuck in a paper bag a few times, I think this is a very narrow way to view others.
I don't know the optimal way to interview engineers. I do know the style of interview that I prefer and excel at[0], but I wouldn't be so naive to think that the style that works for me would work for all. Often I chuckle about an anecdote from the fabled I.P. Sharp: Ian Sharp would set a light meter on his desk and measure how wide an interviewees eyes would get when he explained to them about APL. A strange way to interview, but is it any less strange than interviewing people via leetcode problems?
0: I think my ideal tech screen interview question is one that 1) has test cases 2) the test cases gradually ramp up in complexity 3) the complexity isn't revealed all at once; the interviewer "hides their cards," so to speak 4) is focused on a data structure rather than an algorithm such that the algorithm falls out naturally rather than serves as the focus. 5) Gives the opportunity for the candidate to weigh tradeoffs, make compromises, and cut corners given the time frame. 6) Doesn't combine big ideas (i.e. you shouldn't have to parse complex input and do something complicated with it); pick a single focus. Interviews I have participated and enjoyed like this: construct a Set class (union, difference, etc); implement an rpn calculator (ramp up the complexity by introducing multiple arities); create a range function that works like the python range function (for junior engineers, this one involves a function with different behavior based on arity).
But more than that, when he's a little older, how would he call anyone to get help? When a phone is locked, you can call 911, but it's not really obvious how. A landline would be a nice big target.
That said, our house, despite being a century old, doesn't have a single phone jack. I've been thinking about running an ethernet line for a VoIP phone, but they are pretty "buisness-y" and not the nicest to look at. Does anyone have a recommendation for a simple to use/nice to look at VoIP phone?
EDIT: Looks like there are adapters that take ethernet in (and I could split the PoE for power too) and go out to a phone cord. I would probably want to terminate it to a wall plate, but then I could just buy any old phone I liked.
The current state of interviews tells me that a lot of programmers prefer to think of it as software “engineering” rather than as a craft or trade. If creativity meant something to them, I wouldn’t spend all my time bored silly trying to memorize algorithms.
What I find a pain is the uneven support for shared workers.