mcgwiz

Joel is a great but credit for this goes to Rico Mariani, originally quoted here https://web.archive.org/web/20100514093413/http://blogs.msdn...

</aside>

tl;dr: crowdsourced microblogging platform that encourages inter-community dialogue. I.e. wrest the very fate of your causes back from self-serving officials, celebrities, and mass media!

It started as a side project 10 years ago, before I took some time off to try to build it into something more. Alas I knew far too little of marketing and customer development.

https://www.wiumlie.no/2006/phd/

A link can refer to a user profile page or a news article. Both use the generic anchor "component", which comes from the wider universe of components applicable to most/all HTML docs. HTML: `<A class="user">`, CSS selector: `A.user`.

To extend this, a media card could represent a video or a book or a sidebar item. Both use the media card component's HTML structure but can be tweaked visually with CSS. The root element of the video media card would be `<DIV class="MediaCard video">` and would be identified with the selector `DIV.MediaCard.video`.

(PascalCase is arbitrary but I like that it harks to class naming conventions from OOP languages. You'd need some other naming conventions as well. I like `_title` for internal element class names, like private class members from OOP languages. Internal selectors would be built using the performant child combinator. Some of these patterns are more verbose than current alternatives, but it's also the minimum necessary to get crystal clarity around inherited and cascaded values. Preprocessor nesting makes this less painful. And `-highlight` for variants, because they resemble CLI switches. What about non-generic components? Those aren't "components" as defined here - they are simply higher-level HTML fragments, typically organized in source as an HTML template.)

This gives you two dimensions along which to flexibly organize things - the generic forms and the domain-specific applications, and should keep you from slipping down the slope to utility-dominant CSS.

Commit logs will have the greatest detail, but they also are the costliest to dig up, often requiring multiple rounds of `blame`. They are therefore most appropriate to include information pertinent at integration-time, namely code review context/justifications.

Merge commits (such as those created during typical PR/MR merges) have similar potential to include explanatory background, but at a coarser granularity, e.g. feature level.

Expectations of one's job are vastly different (fulfill all of my personal needs versus provide financial stability to support my personal life; work-life blend versus work-life balance).

Ethics are different (Adderall will get me through crunch time versus ugh! crunch time!; give me little projects like I had in college versus give me an area of responsibility and a mandate).

Standards are different (this project will be dead/replaced in a year, or I'll be at a new gig, so building quality is a waste versus always build quality, the definition of which I've determined based on decades of experience).

There's a gap of political perspective as well (boomers and, to an extent, Gen-Xers screwed up the world versus inheriting the established business/social order was generally accepted).

Easiest to understand is a vast difference in language and cultural reference points - not as different as an ESL candidate but on that same spectrum.

Reasi is revolutionizing real estate with a modern, secure, and convenient transaction platform. We're early stage but have already received backing by big players, such as renowned proptech accelerator MetaProp. Compensation is a healthy mix of cash and equity (up to 3%) - ideal for the senior developer tired of building other people's ideas without sharing in the potential for profits.

Obligatory "ideal candidate" laundry list - you don't need all to apply if you're an aggressive learner:

• 5+ years tech leadership on nontrivial projects (not necessarily all successful)

• Expertise in most of: PostgreSQL, Node.js, React, TypeScript / modern JavaScript, Solidity, Jest, Docker, networking / HTTP, OOP / FP / infrastructure patterns and practices

• Expertise in one of: real estate domain, blockchain development, DevOps / site reliability, IA / UX / UI design, data science

• Multidisciplinary interest beyond the code, e.g. focusing on product, improving the business, and devising solutions to real estate problems

• Obsession with detail and quality

• Strong technology opinions (weakly held) and courage to raise concerns

Your primary responsibility will be to develop the core application suite, infrastructure, and tooling that powers our P2P blockchain escrow platform. Additionally, you will provide strategic input to the business and our engineering culture.

We focus on results, continuously improve ourselves, and derive strength from diverse backgrounds and experiences. Drop us a line at [email protected]!

Reasi is revolutionizing real estate with a modern, secure, and convenient transaction platform. We're early stage but have already received backing by big players, such as renowned proptech accelerator MetaProp. Compensation is a healthy mix of cash and equity (up to 3%) - ideal for the senior developer tired of building other people's ideas without sharing in the potential for profits.

Obligatory "ideal candidate" laundry list - you don't need all to apply if you're an aggressive learner:

• 5+ years tech leadership on nontrivial projects (not necessarily all successful)

• Expertise in most of: PostgreSQL, Node.js, React, TypeScript / modern JavaScript, Solidity, Jest, Docker, networking / HTTP, OOP / FP / infrastructure patterns and practices

• Expertise in one of: real estate domain, blockchain development, DevOps / site reliability, IA / UX / UI design, data science

• Multidisciplinary interest beyond the code, e.g. focusing on product, improving the business, and devising solutions to real estate problems

• Obsession with detail and quality

• Strong technology opinions (weakly held) and courage to raise concerns

Your primary responsibility will be to develop the core application suite, infrastructure, and tooling that powers our P2P blockchain escrow platform. Additionally, you will provide strategic input to the business and our engineering culture.

We focus on results, continuously improve ourselves, and derive strength from diverse backgrounds and experiences. Drop us a line at [email protected]!

Prescriptively, HTML was designed to be used a certain way. "Proper" use of it supports a variety of use cases beyond graphical browser-based publications and applications.

Descriptively, there is no "right" or "wrong", "proper" or "improper". <div>s and <span>s are often enough because they get The Job™ done, for some critical subset of all "jobs." It is true that web scraping and machine parsing of content becomes harder when tags aren't applied semantically, and that text- and speech-based browsing is more difficult. It would seem that those needs are simply not substantial enough to the commissioners of web development work to warrant the extra attention and care, especially in the hyper-competitive, sink-or-swim environment of tech startups.

It is (nominally) what it is (actually).

The real problem is a lack of exploitation and education of the secondary applications of semantic HTML and how it fits in with related technologies (HTTP headers vs <META>, URLs and fragment identifiers, microformats and CSS semantic class naming) by product designers. This would naturally drive developer interest. In the meantime, those who do understand these things can continue to devise solutions orders of magnitude more efficient or effective.

Reasi is revolutionizing real estate with a modern, secure, and convenient transaction platform. We're early stage but have already received backing by big players, such as renowned proptech accelerator MetaProp. Compensation is a healthy mix of cash and equity (up to 3%) - ideal for the senior developer tired of building other people's ideas without sharing in the potential for profits.

Imaginary "ideal candidate" laundry list - you don't need all to apply if you're an aggressive learner:

• 5+ years tech leadership on nontrivial projects (that were not necessarily all successful)

• Expertise in most of: PostgreSQL, Node.js, React, TypeScript / modern JavaScript, Solidity, Jest, Docker, networking / HTTP, OOP / FP / infrastructure patterns and practices

• Expertise in one of: real estate domain, blockchain development, DevOps / site reliability, UX / UI design

• Multidisciplinary interest beyond coding, e.g. focusing on product, improving the business, and devising solutions to real estate problems

We focus on results, continuously improve ourselves, and derive strength from diverse backgrounds and experiences. Drop us a line at [email protected]!