Web Components are not Framework Components — and That’s Okay • Lea Verou
Disclaimer: This post expresses my opinions, which do not necessarily reflect consensus by the whole Web Components community. A blog post by Ryan Carniato titled “Web Components Are Not the Future†has recently stirred a lot of controversy. A few other JS framework authors pitched in, expressing frustration and disillusionment around Web Components. Some Web Components folks wrote rebuttals, whil
It’s Time To Talk About “CSS5†— Smashing Magazine
Have you ever wondered what happened after CSS3? It’s common knowledge that we never saw CSS4 come after it, yet we have a plethora of new features that have no similar way of defining when they were introduced. The W3C CSS-Next community group is actively searching for better approaches for how we describe the evolution of CSS over time and identify feature sets as effectively as we did with CSS3
Why Patching Globals Is Harmful
Honestly, I'd never thought I'd be writing about this, but the matter of patching globals turned out to be one of those topics that a lot of engineers seem to misunderstand. Most of us don't do monkey-patching, and even fewer stay around those implementations long enough to witness their impact. All the more reason to talk about it. Throughout the next few thousand words, I will be referring to mo
åŠå·å“也「仮説ã¯ã“ã¨ã”ã¨ã外れãŸã€ãã‚Œã§ã‚‚ブレãšã«é–‹ç™ºã§ãã‚‹ç†ç”±ã¯ï¼Ÿã€å¾Œç·¨ã€‘ - エンジニアtype | 転è·type
2024.04.08 åƒãæ–¹ åŠå·å“也PdMプãƒã‚°ãƒ©ãƒŸãƒ³ã‚°ãƒ—ãƒãƒ€ã‚¯ãƒˆ å‰ç·¨ã«ç¶šã„ã¦åŠå·å“也ã•ã‚“ã«ãƒ—ãƒã‚°ãƒ©ãƒŸãƒ³ã‚°åˆå¦è€…å‘ã‘ã®å¦ç¿’サービス『Jasmine Teaã€ã®ã“ã®1å¹´ã‚’èžã。リリースã‹ã‚‰ã¡ã‚‡ã†ã©1å¹´ãŒçµŒã£ãŸã€ŽJasmine Teaã€ã ãŒã€Œå®Ÿã¯æ€ã£ã¦ã„ãŸã‚ˆã‚Šã†ã¾ãã„ã£ã¦ã„ãªã„ã€ã®ã ã¨ã„ã†ã€‚未知ã®æŒ‘戦ã«èª²é¡Œã¯ã¤ãã‚‚ã®ã§ã¯ã‚る。åŠå·ã•ã‚“らã¯ã©ã‚“ãªèª²é¡Œã«ã¶ã¤ã‹ã‚Šã€ãã‚Œã¨ã©ã†å‘ãåˆã£ã¦ã„ã‚‹ã®ã ã‚ã†ã‹ã€‚ 事å‰ã«ç«‹ã¦ãŸä»®èª¬ã®ã“ã¨ã”ã¨ããŒå¤–ã‚ŒãŸã“ã¨ã€ãã‚Œã§ã‚‚ブレãšã«é–‹ç™ºã‚’続ã‘られã¦ã„ã‚‹ç†ç”±ã€å°‘ã—脇é“ã«é€¸ã‚Œã¦ã€ç”ŸæˆAI時代ã®ã‚¨ãƒ³ã‚¸ãƒ‹ã‚¢ã«å¿…è¦ãªã“ã¨ã‚‚伺ã£ãŸã€‚ Tablyæ ªå¼ä¼šç¤¾ 代表å–ç· å½¹ Technology Enabler åŠå· å“也ã•ã‚“（@takoratta） 早稲田大å¦ç†å·¥å¦éƒ¨å’æ¥ã€æ—¥æœ¬DECを経ã¦Microsoftã«è»¢è·ã€‚Windowsã®é–‹ç™ºã«æºã‚ã‚Šã€ãã®å¾ŒGoogleã§ã¯ãƒ—ãƒãƒ€ã‚¯ãƒˆãƒžãƒã‚¸ãƒ¡ãƒ³ãƒˆ
YX problem | Structure and Interpretation of Computer Programmers
Software people are always all up in the XY problem: someone asks about how to do X when what they’re really trying to solve is Y. I find the YX problem much more frustrating: where software people decide that they want to answer question Y even though what someone asks is question X. I’ve seen a few different manifestations of this pattern: Respondent doesn’t know the answer to X, but does know t
GraphQL is for Backend Engineers | Apollo GraphQL Blog
Most articles explaining the benefits of GraphQL focus on advantages for the frontend: things like preventing overfetching, reducing round trips, and iterating faster. But GraphQL provides just as many advantages for backend developers, which is why I choose it by default for new APIs and why you should consider it, too. Improved communication The goal of building any API is to enable someone to u
What it was like working for GitLab
February 8, 2024 I joined GitLab in October 2015, and left in December 2021 after working there for a little more than six years. While I previously wrote about leaving GitLab to work on Inko, I never discussed what it was like working for GitLab between 2015 and 2021. There are two reasons for this: I was suffering from burnout, and didn't have the energy to revisit the last six years of my life
The Performance Inequality Gap, 2024 - Infrequently Noted
The global device and network situation continues to evolve, and this series is an effort to provide an an up-to-date understanding for working web developers. So what's changed since last year? And how much HTML, CSS, and (particularly) JavaScript can a new project afford? The Budget, 2024 JavaScript-Heavy Markup-Heavy Calculate Your Own Situation Report Mobile Desktop Takeaways The Great Branch
The Open Source Sustainability Crisis
tl;dr What is Open Source sustainability? Fair pay, no hoops. Why is it in crisis? Burnout. Okay, now let’s talk about the Open Source sustainability crisis. The purpose of this post is to define terms. What is Open Source sustainability? Why do I say it is in crisis? My answers are that sustainability is when people are getting paid without jumping through hoops, and we’re in a crisis because peo
糸井 é‡é‡Œ on Twitter: "ã‚らãŸã‚ã¦ã€ã¾ãŸæ€ã„ã¾ã™ã€‚ã¼ãã¯ã€ã˜ã¶ã‚“ãŒå‚考ã«ã™ã‚‹æ„見ã¨ã—ã¦ã¯ã€ã€Œã‚ˆã‚Šã‚¹ã‚ャンダラスã§ãªã„ã»ã†ã€ã‚’é¸ã³ã¾ã™ã€‚「より脅ã‹ã—ã¦ãªã„ã»ã†ã€ã‚’é¸ã³ã¾ã™ã€‚「よりæ£ç¾©ã‚’語らãªã„ã»ã†ã€ã‚’é¸ã³ã¾ã™ã€‚「より失礼ã§ãªã„ã»ã†ã€ã‚’é¸ã³ã¾ã™ã€‚ãã—ã¦ã€Œã‚ˆã‚Šãƒ¦ãƒ¼ãƒ¢ã‚¢ã®ã‚ã‚‹ã»ã†ã€ã‚’é¸ã³ã¾ã™ã€‚"
ã‚らãŸã‚ã¦ã€ã¾ãŸæ€ã„ã¾ã™ã€‚ã¼ãã¯ã€ã˜ã¶ã‚“ãŒå‚考ã«ã™ã‚‹æ„見ã¨ã—ã¦ã¯ã€ã€Œã‚ˆã‚Šã‚¹ã‚ャンダラスã§ãªã„ã»ã†ã€ã‚’é¸ã³ã¾ã™ã€‚「より脅ã‹ã—ã¦ãªã„ã»ã†ã€ã‚’é¸ã³ã¾ã™ã€‚「よりæ£ç¾©ã‚’語らãªã„ã»ã†ã€ã‚’é¸ã³ã¾ã™ã€‚「より失礼ã§ãªã„ã»ã†ã€ã‚’é¸ã³ã¾ã™ã€‚ãã—ã¦ã€Œã‚ˆã‚Šãƒ¦ãƒ¼ãƒ¢ã‚¢ã®ã‚ã‚‹ã»ã†ã€ã‚’é¸ã³ã¾ã™ã€‚
å“質ä¿è¨¼éƒ¨é–€ã®é™³è…化。ãã—ã¦é™³è…化ã—ãŸå“質ä¿è¨¼ã¯å“質を悪化ã•ã›ã‚‹ - åƒé‡Œéœ§ä¸
※å“質ä¿è¨¼ã®ã‚¨ãƒ³ã‚¸ãƒ‹ã‚¢ã§ã‚ã‚‹ç†è€…ãŒè‡ªçœãƒ»æˆ’ã‚ã®ãŸã‚ã«æ›¸ã„ãŸè¨˜äº‹ã«ãªã‚Šã¾ã™ å“質管ç†ï¼ˆQuality Control）ã€å“質マãƒã‚¸ãƒ¡ãƒ³ãƒˆã¯å›½å†…ã§ã¯è£½é€ æ¥ã‚’ä¸å¿ƒã«ç™ºå±•ã—ã€ãƒ—ãƒãƒ€ã‚¯ãƒˆã®ç«¶äº‰åŠ›å‘上ã«è²¢çŒ®ã—ã¦ãã¾ã—ãŸã€‚ JTCã¨å‘¼ã°ã‚Œã‚‹æ—§æ¥ã‹ã‚‰ã®ãƒ¡ãƒ¼ã‚«ãƒ¼ã§ã¯ã€ãã®å®Ÿç¸¾ãƒ»å¹´åŠŸã®è“„ç©ã«å¿œã˜ã¦ã€ç‹¬ç«‹æ€§ã‚’ä¿ã£ãŸå“質管ç†ãƒ»å“質ä¿è¨¼éƒ¨é–€ãŒæ¨©å¨ã‚’ç²å¾—ã—ã€ä»Šã§ã‚‚ソフトウェア開発ã«å¼·ã„影響力をä¿æŒã™ã‚‹ã‚ˆã†ã«ãªã£ã¦ã„ã¾ã™ã€‚ç†è€…ã¯è¤‡æ•°ã®ãƒ¡ãƒ¼ã‚«ãƒ¼ã‚’転è·ã‚„コンサルã§å·¡ã£ã¦æ¥ã¾ã—ãŸãŒã€ä¾‹ãˆã°å“質ä¿è¨¼éƒ¨é–€ãŒæ‰¿èªã—ãªã„ã¨ãƒžã‚¤ãƒ«ã‚¹ãƒˆãƒ¼ãƒ³ã§é–‹ç™ºãŒãƒ–ãƒãƒƒã‚¯ã•ã‚Œã‚‹ã€ãƒ—ãƒãƒ€ã‚¯ãƒˆãŒãƒªãƒªãƒ¼ã‚¹ã§ããªã„ã¨ã„ã£ãŸæ¨©é™ã‚’æŒã¤ä½“制ãŒã€ä»ŠãªãŠæ™®éçš„ã«è¦‹å—ã‘られã¾ã™ã€‚ ã“ã®å“質ä¿è¨¼éƒ¨é–€ãŒæ¨©åŠ›ã‚’æŒã¡ã€å“質ゲートã®é–€ç•ªã¨ã—ã¦æŒ¯ã‚‹èˆžã†ä½“制ã¯ã€ä»Šã§ã‚ã£ã¦ã‚‚ã€ã‚ã‚‹é¢ã§æ©æµã‚’æä¾›ã—ã¦ã„ã¾ã™ã€‚例ãˆã°æ¬¡ã®ã‚ˆã†ãªã‚‚ã®ã§ã™ï¼š 法è¦åˆ¶å¯¾å¿œã€æ¨™æº–化対応ã€ãã®ä»–公的ãªã‚¬ãƒãƒŠãƒ³ã‚¹è¦æ±‚ã¸
メンテã®ã„らãªã„ソフトウェア - 誰ã‹ã®å½¹ã«ç«‹ã¦ã°ã„ã„ブãƒã‚°
ソフトウェアエンジニアã¨ã—ã¦åƒã始ã‚㦠20 年以上ã«ãªã‚Šã¾ã™ã€‚ 元々ソフトウェアã§ã„ã‚ã„ã‚作りãŸãã¦å°±ã„ãŸè·æ¥ãªã®ã§ã€çµæ§‹ãªæ•°ã®ãƒ—ãƒãƒ€ã‚¯ãƒˆã‚’開発ã—ã¦ãã¾ã—ãŸã€‚ ç§ãŒãƒ¡ã‚¤ãƒ³ã§é–‹ç™ºã—ãŸã‚‚ã®ã§ OSS ã¨ã—ã¦å‡ºã¦ã„ã‚‹ã‚‚ã®ã§ã¯ã€ yrmcds: memcached クãƒãƒ¼ãƒ³ã§ã€ãƒ¬ãƒ—リケーション機能ãªã©ã‚’æŒã¤ usocksd: SOCKS4/5 サーãƒãƒ¼ & ライブラリ transocks: アプリã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯é€šä¿¡ã‚’é€éŽçš„ã« SOCKS サーãƒãƒ¼ã«ãƒ—ãƒã‚ã‚·ã™ã‚‹é€éŽãƒ—ãƒã‚ã‚· coil v2: Kubernetes ã® CNI ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ‰ãƒ©ã‚¤ãƒ moco: MySQL を自動é‹ç”¨ã™ã‚‹ Kubernetes オペレーター accurate: Kubernetes 上㧠namespace ベースã®ã‚½ãƒ•ãƒˆãƒžãƒ«ãƒãƒ†ãƒŠãƒ³ã‚·ãƒ¼ã‚’実ç¾ã™ã‚‹ãŸã‚ã®ã‚½ãƒ•ãƒˆã‚¦ã‚§ã‚¢ ãªã©ãŒã‚ã‚Šã¾ã™ã€‚ã“れらã®ã‚½ãƒ•ãƒˆã‚¦ã‚§ã‚¢ã®å¤šãã¯ã€ç¾å½¹
スタートアップã«å‚ç”»ã™ã‚‹äººã«ã¨ã£ã¦ã®SOã®æ„義 - SOè¨è¨ˆã§ç¢ºèªã™ã¹ããƒã‚¤ãƒ³ãƒˆï½œSatoshiYamada
今回ã¯ã€ï¼ˆå‰å›žã¨ã¯é€†ã§ï¼‰SOã®ä»˜ä¸Žã‚’å—ã‘る従æ¥å“¡å´ã®è¦–点ã§ã‚¹ã‚¿ãƒ¼ãƒˆã‚¢ãƒƒãƒ—ã«å‚ç”»ã™ã‚‹éš›ã«SOã®ã©ã†ã„ã£ãŸç‚¹ã«ç•™æ„ã™ã¹ãã‹ã€ã¨ã„ã†å†…容を記載ã—ãŸã„ã¨æ€ã„ã¾ã™ã€‚ å‰å›žã®è¨˜äº‹ã§è¨˜è¼‰ã—ã¾ã—ãŸãŒã€SOã¯ã¾ã 資金的ã«ä½™è£•ã®ãªã„スタートアップãŒã€Œä¼šç¤¾ã®ä¾¡å€¤ã‚’大ãã引ã上ã’ã¦ãれる貴é‡ãªäººè²¡ã€ã‚’早期ã‹ã‚‰ä»²é–“ã«è¿Žãˆå…¥ã‚ŒåŒã˜ç›®æ¨™ã‚’å‘ã„ã¦å…¨åŠ›ã§èµ°ã£ã¦ã„ããŸã‚ã®é‡è¦ãªæ‰‹æ®µã§ã™ã€‚ ãã†ã—ãŸè²´é‡ãªäººè²¡ãŒã‚ˆã‚Šæœªæ¥ã‚’作るスタートアップã«å¤šã集ã¾ã£ã¦ã„ã一助ã¨ã—ã¦ã€å¾“æ¥å“¡å´ãŒã©ã†ã„ã£ãŸè¦–点ã§SOã®è¨è¨ˆã‚’見るã®ãŒè‰¯ã„ã‹ã€ã¨ã„ã†ãƒã‚¤ãƒ³ãƒˆã‚’ã“ã®noteã§ãŠä¼ãˆã§ãã‚Œã°ã¨æ€ã„ã¾ã™ã€‚ 以下ã€SOã«ã¤ã„ã¦ã¯æ§˜ã€…ãªè€ƒãˆæ–¹ãŒã‚ã‚‹ä¸ã§ã€ç§è‡ªèº«ã®çµŒé¨“や知見ã«åŸºã¥ãã¨ã“ã‚ãŒå¤§ãã„ã§ã™ãŒã€SO付与ã®ã‚るスタートアップã«å‚ç”»ã™ã‚‹éš›ã«ç¢ºèªã—ã¦ãŠã„ãŸæ–¹ãŒè‰¯ã„ãƒã‚¤ãƒ³ãƒˆã‚’é‡è¦ãªé †ã«è¨˜è¼‰ã—ã¦ã„ãã¾ã™ã€‚ ã¡ãªã¿ã«ï¼ˆèªã‚“ã§é ‚ãå‰ã®å¤§å‰æã¨ã—ã¦ã€ï¼‰ã‚¹ã‚¿ãƒ¼ãƒˆã‚¢ãƒƒãƒ—ã®S
エã‚スパート人æã‚’æ´»ã‹ã™ãƒŠãƒ¬ãƒƒã‚¸ã‚¹ãƒãƒ³ã‚µãƒ¼ã‚·ãƒƒãƒ—制度｜Knowledge Work Developers blog
執ç†è¶£æ—¨ï¼šã‚¤ãƒãƒ¼ãƒ–ルメントã®ãƒ¢ãƒ‡ãƒ«ã‚±ãƒ¼ã‚¹ã‚’示ã™ãƒŠãƒ¬ãƒƒã‚¸ãƒ¯ãƒ¼ã‚¯ HR Manager 徳田ã§ã™ã€‚ 今回ã®Developers Blogã¯ã€ã‚¨ã‚スパート人æã®æ´»å‹•ã‚’支æ´ã™ã‚‹ã€ŒãƒŠãƒ¬ãƒƒã‚¸ã‚¹ãƒãƒ³ã‚µãƒ¼ã‚·ãƒƒãƒ—制度ã€ã‚’紹介ã—ã¾ã™ã€‚ ナレッジワークã¯ä»•äº‹ã®ã‚¤ãƒãƒ¼ãƒ–ルメント(能力ã®å‘上やæˆæžœã®å‰µå‡º)をコンセプトã¨ã—ãŸä¼æ¥å‘ã‘ソフトウェアを開発・æä¾›ã—ã¦ã„ã¾ã™ã€‚ コーãƒãƒ¬ãƒ¼ãƒˆéƒ¨é–€ã¯ã€Œã‚¤ãƒãƒ¼ãƒ–ルメントã®ãƒ¢ãƒ‡ãƒ«ã‚±ãƒ¼ã‚¹ã‚’示ã™ã€ã‚’ミッションã¨ã—ã¦æŽ²ã’ã€ãƒŠãƒ¬ãƒƒã‚¸ãƒ¯ãƒ¼ã‚¯ãŒã‚¤ãƒãƒ¼ãƒ–ルメントを体ç¾ã™ã‚‹ãƒ¢ãƒ‡ãƒ«ã¨ãªã‚Œã‚‹ã‚ˆã†ã«çµ„織作りã«å–り組んã§ãŠã‚Šã€2022å¹´10月-12月ã®3ヶ月間ã§ã‚‚計8ã¤ã®åˆ¶åº¦ã‚’社内リリースã—ã¾ã—ãŸã€‚ ãã®ã†ã¡ã®1ã¤ãŒã€ŒãƒŠãƒ¬ãƒƒã‚¸ã‚¹ãƒãƒ³ã‚µãƒ¼ã‚·ãƒƒãƒ—制度ã€ã§ã™ã€‚ 制度内容ã¯ã‚·ãƒ³ãƒ—ルã§ã€Œä¸–ã®ä¸ã¸ã®ãƒŠãƒ¬ãƒƒã‚¸ã‚·ã‚§ã‚¢ã®ãŸã‚ã®ç¤¾å¤–活動ã«ã¤ã„ã¦ã€æ¥å‹™æ™‚é–“åˆ©ç”¨ã‚„ä¼šç¤¾è²»ç”¨è² æ‹…ç‰ã‚’èªã‚ã‚‹ã“ã¨ã§æ”¯æ´ã™ã‚‹ã€ã¨ã„ã†ã‚‚ã®ã§ã™ã€‚ 制度ã¯ã‚·ãƒ³ãƒ—
Maybe Getting Rid of Your QA Team was Bad, Actually.
Over many years, “DevOps†practitioners applied Theory Of Constraints to our problems, ruthlessly optimizing our delivery pipelines and practices. Manual release management? Hell no, automate that. Deployment? Automate that too. Image management? 🔨 No thanks. Rolling back after we trebuchet a flaming dumpster into production? Automated. Whatever low value activity we could find in the process of
The Engineer/Manager Pendulum
charity.wtf charity wtf's about technology, databases, startups, engineering management, and whiskey. Lately I’ve been doing some career counseling for people off Twitter (long story). The central drama for many people goes something like this: “I’m a senior engineer, but I’m thinking about being a manager. I really like engineering, but I feel like I’m just solving the same problems over and over
The Product-Minded Software Engineer
Product-minded engineers are developers with lots of interest in the product itself. They want to understand why decisions are made, how people use the product, and love to be involved in making product decisions. They're someone who would likely make a good product manager if they ever decide to give up the joy of engineering. I've worked with many great product-minded engineers and consider myse
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
Design System Generations
I work with the regulated drug development industry, and believe there is a usef... | Hacker News
Stop paying tech debts, start maintaining code
{{#tags}}- {{label}}
{{/tags}}