antibland

…but I wasn’t able to scroll any further on the page

  * { 
    overflow: auto !important;
  }

Were you looking for work when FB approached you either time? If so, why would you take yourself out of the running given you’re (I’m assuming) an experienced developer?

On my iPhone SE (mobile Safari), elements are being truncated on the right side of the screen, meaning I can’t view all the data. I’m not near a laptop right now, but I wonder if you’re forgetting:

  * { box-sizing: border-box: }

Great work! I would add that you should turn off auto-capitalization for tablet/mobile devices, to preserve the shell aesthetic.

  <input type="text" autocapitalize="off />

I’m curious about the pool of Facebook users who seldom use the product, retaining it solely for groups and to keep in touch with family. Will this event loosen that final brick and drive these users to delete their accounts?

For custom CSS in Safari: Preferences => Advanced => Stylesheet dropdown

Large-scale seawater desalination.

...we’ve built programs that just dont talk to each other at all.

This really struck me, the idea that perhaps software mirrors the human experience. In the US, we've traded tribalism for individualism, open discussion for echo chambers, and the exchange of beliefs for the walled garden of one's personal vision.

"I don't care about online privacy because I have nothing to hide."

This persona's ethos is finally starting to show visible cracks.

It's sad how these valuable optimizations are unknown to the average person. When I hear "the browser" discussed in almost any parlance, the implication is Chrome. It's rare to even hear someone say "Chrome," as it's the defacto choice for the non-mobile web. Convenience breeds ignorance.

Why is this submission[0] flagged, yet this is not? Because of the word "black"?

[0] https://news.ycombinator.com/item?id=23950661

Carousels are the type of UI pattern that is only okay if you ask for it. Amazon is a good example of a carousel done right. If I want to see the full-sized images which are part of a customer's product review, I click on the thumbnail representing these images, with the expectation that some larger, more obvious version of the images will be made available. Once a carousel appears in an overlay, it's not disturbing or annoying at all. It's there because I asked for it.

AJAX is a new technique for creating better, faster, and more interactive web applications with the help of XML, HTML, CSS, and JavaScript.

AJAX first appeared in 1999 [0], when people still ate Olestra and used pagers.

[0] https://en.m.wikipedia.org/wiki/Ajax_(programming)

Tech shops keep asking for more and more, beneath the ever-widening "full stack" moniker, and we developers do our best to oblige them. But, clearly, critical decisions are being made (or not) by people who are inexperienced yet afraid to ask for help. Maybe it's time to hire more "I-shaped" developers, rather than an org full of shaky generalists.

Amazing examples. Great library. Coupled with the Intersection Observer API[0], this software could add a lot of value to an instructive app or website. Imagine these beautiful annotations tastefully animating as various elements are observed as the user scrolls.

[0] https://developer.mozilla.org/en-US/docs/Web/API/Intersectio...

FB can utilize Giphy for pixel tracking (similar to FB Like button) since these low-brow, comedic incantations appear all across the webosphere.

Great advice as always (newsletter subscriber). The other piece of advice I offer is to join Stack Overflow and answer a few questions a week. This helps reinforce skills, understand common developer pain points, and can occasionally lead to a job offer.

One reason why we may have one line packages is the demand FAANG places on applicants. On three job screens from three different companies, I was asked, "Which npm packages have you created that we'd know about?"

For many who are hell-bent on entering these companies, yet have no known packages under their belt, they very well might fire off a one line package that actually gets some downloads, to be better "prepared" when screened.

It was important to show one's dueling prowess, but also that one was capable of taking the wound that was inflicted.

The modern day engineering equivalent to this is HackerRank.

While articles like this always bring a smile, I'm saddened for the animals, knowing that their ecological reprieve will soon be dashed by human recklessness. I've actually begun to enjoy many aspects of the quarantine, and would like it to continue a lot longer. The planet is better off without us.

I would argue that the last battle was what the US saw occur in China and Italy. We knew the virus would reach us within weeks of those countries being hit, knew the risk potential of it, but did little to adequately prepare.

If anyone knows how to deftly bow out of a forced company outing, I'd love to know your method. Last time I tried to get out of one of these things, I informed one of the owners I had too much to do and needed to spend the day catching up on work.

She was furious and told me I was "damaging the culture."

Location: Portland, OR

Remote: Preferred

Willing to relocate: Yes (outside of US)

Technologies: JavaScript (Express, React, Gatsby), GraphQL, MongoDB, Advanced CSS, WAI-ARIA

Experience: 20 years

Website: https://andyhoffman.codes

Résumé/CV: https://andyhoffman.codes/Andy_Hoffman_CV.pdf

Email: andy@andyhoffman.codes

For anyone wondering how well supported these features are globally (from caniuse):

prefers-color-scheme: 80.85%

prefers-reduced-motion: 84.05%

Payment Request API: 90.06%

Web Share API: 49.25%

Push API: 78.57%

Service Workers: 94.42%

Web/native app install banners: 68.19%

Get Installed Related Apps API: Not launched, 0%

WebXR: 61.83%

Picture-in-Picture: 85.01%

Media Session API: 66.31%

Chrome Sender API: 64.75%

AirPlay: Unknown

Force Touch API: 55.74%

AR Quick Look: Unknown

GamePad API: 95.18%

WebUSB API: 65.27%

Web Bluetooth API: 68.6%

Web Locks API: 67.43%

Keyboard Lock: 30.47%

Generic Sensor API: 67.43%

Credential Management API: 70.86%

Clipboard API: 70.86%

Presentation API: 15.24% full support, 80.14% partial

Screen Orientation API: 76.16%

getUserMedia camera selection: 93.48%

Pointer Lock (Mouse Lock): 55.06%

Theme Color: 37.39%

Vibration API: 77.13%

Web Coffee API: Unknown

Battery Status API: 72.36%

Page Visibility API: 97.44%

Web Speech API: 92.88%

  Location: Portland, OR
  Remote: Preferred
  Willing to relocate: Only outside of US
  Technologies: HTML5/CSS/ES7+, React, Gatsby, MongoDB, Node, Modern CSS, WAI-ARIA
  Résumé/CV: https://andyhoffman.codes/Andy_Hoffman_CV.pdf
  Email: andy@andyhoffman.codes

A friend of mine new to CSS was rebuilding the Google homepage using Flexbox. He asked me why Google uses <center> in their HTML, to which I told him it's most likely due to compatibility. Google is accessed by every web capable device and browser ever made. Yet, seeing <center> feels unacceptable.

In the Twitter thread (regarding Fama):

You can opt out of our service by contacting us at privacy@fama.io as long as you have not provided written consent to one of our clients so Fama may access this information on your behalf.

The color palette is really easy on the eyes. I have a few criticisms, though, all related to the cards under "Recent Articles":

1. In tablet size, the content of <h2>s get lost beneath the top of the card.

2. Even in desktop size, the spacing at the top of the cards looks off. Longer strings cause visual unevenness. CSS Grid should be able to fix the header spacing issues within cards.

3. Hard-coding the height of the cards is probably a mistake. Content should govern the height of the card, so actions such as user zoom or browser-level font size increases, scale the padding of the card appropriately.

4. When hovering over any part of the card, the hover style kicks in and the card text content raises slightly. This is usually a hint to the user that an action can be performed, like a click which follows the href. However, the user must click directly on the <a> inside of the <h2> to follow the link. I recommend making the entire card clickable, so the hover style seems more intentional. Otherwise, I would remove the hover style.

This is such a victimhood mentality and a ridiculous statement.

Do you think you'd say this to the poster's face in an in-person conversation? I find it's too easy to communicate in this way on the Internet, but it appears hurtful and over-the-top. Nasty comments can affect peoples' lives and we rarely see the fallout of how we hurt others in this way. Let's all tread more carefully and be a little nicer to each other.

For the button wrapped in a link example [0], which is invalid HTML, many people don't know it's valid to wrap a button inside a form, using the form's action as the destination. Not something I use often, but it's at least a thing worth knowing.

<form action="link.html" method="get" target="_blank"> <button type="submit">Link</button> </form>

[0] https://www.htmhell.dev/4-link-also-button/