“The noise that TikTok Shop has raised about the future of #LiveShopping” … “in Europe is just that: noise.

FREIM Studio speaks with our CEO Alfredo Ouro and they are optimistic: 


LiveShopping is the future of eCommerce worldwide.” —@onlive_site

https://medium.com/@freim.studio/the-future-of-live-streaming-2022-73d91614d6df

A friendly reminder to don't change the z-index like gambling with the highest value, if it doesn't work as expected check the stacking context of the early elements in the hierarchy.
`position` is just one of the attrs creating stacking contexts. e.g. check `isolation`. #webdev


https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Positioning/Understanding_z_index/The_stacking_context

https://developer.mozilla.org/en-US/docs/Web/CSS/isolation


This is basic stuff for a lot of developers but is often misused anyway. Yes, read this whole thing first or continue gambling. 😉
https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Positioning/Understanding_z_index 

Stacking and z-index in CSS

As an evolutionary step from the first move from Material Icons to @googlefonts, they evolve traditional icon format with variable fonts technology to improve their design flexibility, user experience, and accessibility benefits.

Material Symbols font is the variable version of the Material Icons font. It's customizable.

Previously:
https://twitter.com/nilsandrey/status/1372417009464541184?s=19

Then:
https://twitter.com/googlefonts/status/1516934123700383744?s=19

https://twitter.com/materialdesign/status/1517533692712869888?s=19

https://twitter.com/materialdesign/status/1519013484960354304?s=19

Material Symbols font

2022 Ruby on Rails Community Survey Results
"While Rails is no longer the new kid on the block, it's proven to be a reliable framework that can scale up with large companies (Procore, Shopify, GitHub)..." via @planetargon

Sample question: "What JavaScript libraries are you using alongside Rails?" https://rails-hosting.com/2022#what-javascript-libraries-are-you-using-alongside-rails #RailsSurvey2020 via @planetargon

Sample question: "What are some technical podcasts that you enjoy listening to?" https://rails-hosting.com/2022#what-are-some-technical-podcasts-that-you-enjoy-listening-to #RailsSurvey2020 via @planetargon

2022 Ruby on Rails Community Survey Results

🐳 @Docker desktop is available for Linux.

Some Docker Desktop v4.8.* highlights:
- Docker Desktop for Linux
- Extensions in beta
- Compose V2 is now GA

🧵

Announcing Compose v2 General Availability
 
v1 deprecated. Use `docker compose` instead of `docker-compose`, but you can config an alias to both use v2 and, in most cases, you won’t need to do anything different. Can run Commands without a Compose file.

https://www.docker.com/blog/announcing-compose-v2-general-availability/

Docker Desktop for Linux is now in beta and includes Compose v2. 
https://docs.docker.com/desktop/linux/

"Alternatively, you can manually install Docker Compose V2 for Linux."
Install Docker Compose | Docker Documentation: https://docs.docker.com/compose/install/

Docker Extensions are available in beta to extend Docker Desktop's capabilities. There's an SDK to build new ones.

https://docs.docker.com/desktop/extensions/

Docker desktop v4.8

In @nextjs with @typescript, if you import outside your nextjs app folder (like in mono repos or mixing frameworks at code level instead "npming" components for whatever reason), you may receive an error due to the build process not recognizing ts files outside base paths.

e.g.: `import { member } from '../../lib/model/m1';`

Error message: "Module parse failed: You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file"

You can use an alias and `config . resolve . alias` in config.

Full sample at a code gist with a ref link to the author's solution (provided at @vercel/nextjs issues by @LincolnWDaniel at a different context but with similar solution).

💻Use of config.resolve.alias in NextJS config
https://gist.github.com/nilsandrey/ebcae24d844e76915e60047e5b63190b

"No loaders are configured to process this file" in React/NextJS

My friend @apopoutsis wrote about why he largely stopped using To-Do comments in code, and ask about the preferred way to track the to-do list of others in the codebases. ↓

TL;DR: explicit and tool-aided issue management is healthier. 
📄 https://apop.tech/posts/why-i-stopped-using-to-do-code-comments/ (@apopoutsis)

I also believe it, but I usually don't hold myself from taking // notes, on the heat, side by side with the code. Then unused for months (until I got tools and discipline).

We're not the only ones 😅 

The Chromium Project has +30k...
HN: https://news.ycombinator.com/item?id=22339619 
TG: https://www.tickgit.com/browse?repo=github.com/chromium/chromium

The Linux codebase has over 3k TODO comments, many from over a decade ago...
HN: https://news.ycombinator.com/item?id=21910391
TG: https://www.tickgit.com/browse?repo=github.com/torvalds/linux

*TG: Those reports were made with the open-source tool @tickgit_todos to view TO-DO-based pending tasks, progress reports, completion summaries and historical data (using `git` history). You can use that tool.💡
https://twitter.com/tickgit_todos/status/1367662352842231808?s=20

My personal setup is with a to-do's lister extension on the IDE,  manually converting every major task to the issue tracker, and treating the rest as part of the technical debt.

Either way, don't use what you won't pay attention to, @apopoutsis has some implicit rationale here. 

For teams using Github, you can use a "TODO to Issue" action that will convert newly committed to-do comments to GitHub issues on push and can be config to close the issues if the items are removed in a future commit.

https://github.com/marketplace/actions/todo-to-issue

For teams using @Jira, the @Atlassian's extension for @code can be used to create issues from to-do comments. They may have similar tools for other developer environments (or API).

https://marketplace.visualstudio.com/items?itemName=Atlassian.atlascode

To do or not

Another data loss related yesterday, human error vs UX features this time. A popular project on Github lost information. Their complaint comes in a form of a very positive blog post.
↓ 

“Lesson #2: Database design
Use soft-deletes. People are human and they make mistakes. For hard-deletes, delay the process.” — @jakubroztocil at 📄How we lost 54k GitHub stars in @httpie blog post 
↓

soft-deletes are an interesting and challenging technique. I personally prefer a balance like in a "recycle bin approach", to keep deleted records for some time, but maybe it all depends on the specific application.
↓

I've seen implementations based not on marking the records but moving them to a different table which makes a lot of sense to me, bc all the potential rules you can skip like replication, caching, log shipping, etc. Also easing the application of new ones like retention.
↓

👀 “While the author clearly feels bad about the fact that they've lost his community and that GitHub didn't restore it”…“they're also focusing towards the future and using their personal xp as a parable all of us can learn from.”—vaishnavsm at HN https://twitter.com/jakubroztocil/status/1514735329323933703
↓

Personally, I think GitHub makes it pretty hard to make this mistake already, so agreed with making sure you're not on autopilot when taking potentially dangerous actions. (with credits to cmeacham98 at HN)
↓

Anyway, also believe expecting users to stop making mistakes is much less effective than improving the software that amplifies those mistakes into irreversible impacts. Of course, is a very unselfish thought. (with credits to wpietri at HN)
↓

Read the issue with lessons and reflections from @jakubroztocil and @httpie at https://httpie.io/blog/stardust
↓

You can check the HN discussion 
https://news.ycombinator.com/item?id=31033758 at hacker.news.
🔥1617 points, +500 comments in 17 hours 
https://news.ycombinator.com/item?id=31033758
↓

Back to our #DataTalk and the soft delete pattern, we have a lot of options to seize on, with more or less use of the technologies' offerings at each layer and stack. I collected some tweets for us:
https://twitter.com/nilsandrey/timelines/1514993095959617537
▮

Soft delete pattern

Mine too. With the current search features, you can treat Twitter perfectly like a database you're querying and at a consumer level.  ⤸ https://twitter.com/jack/status/1512780764936560644

QT sample here for "original tweets in which someone "@" you", answering a friend:

&gt; (@...) -from:@... -filter:replies

https://twitter.com/nilsandrey/status/1439426222023454720
⤸

Search sample linked here "quoting any tweet from you"

&gt; twitter . com/nilsandrey/ -from:nilsandrey 

It's a derived one from searching with a tweet URL which gives you all its QTs.

https://twitter.com/search?q=twitter.com%2Fnilsandrey%2F%20-from%3Anilsandrey&src=typed_query&f=live

Twitter search tips

How to upload a file or a folder to @awscloud S3 from @gitlab CI using AWS CLI v2* by @vdespa  

https://link.medium.com/AgxkO8Nt4ob 

*v2: Use the AWS' provided official @Docker image tagged `amazon/aws-cli` instead of installing aws-cli onto another one.

It worked like charms for me.