# adopting Published articles for adopting. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Using AI Tools at Work with Balanced Expectations DevFeed: [Using AI Tools at Work with Balanced Expectations]() Original publisher: [Read original article]() Author: Manideep Polireddi Published: 2025-04-21T14:22:00Z Content type: opinion Language: en Sources: [@okmanideep]() Topics: [Artificial Intelligence](), [Large Language Model]() Tags: [adopting](), [ai](), [ai-at-work](), [llms](), [work]() ### AI overview The article argues that people should treat AI tools and LLMs as fast, always-available interns whose output is usually useful but rarely exceptional. This framing encourages cautious adoption, verification, and using any saved time to improve core work. ### Source excerpt A mindset to have balanced expectations about adopting AI at work ## Why Kotlin Multiplatform Teams Should Share Source, not Binaries - Kevin Galligan DevFeed: [Why Kotlin Multiplatform Teams Should Share Source, not Binaries - Kevin Galligan]() Original publisher: [Read original article]() Published: 2024-07-24T00:00:00Z Content type: opinion Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [multiplatform](), [Kotlin](), [Mobile](), [kotlin-multiplatform-libraries](), [Developer experience]() Tags: [adopting](), [challenges](), [debugging](), [ios](), [kmmbridge](), [kotlin](), [kotlin-multiplatform](), [libraries](), [mobile](), [mobile-apps](), [multiplatform](), [native](), [xcode]() ### AI overview The article explains why the authors changed their recommendation for native mobile teams evaluating Kotlin Multiplatform: share Kotlin source code instead of only publishing binary dependencies. Source lets iOS developers browse and debug the Kotlin code, while GitPortal supports versioned source publishing based on Git tags. ### Source excerpt Virtually all native mobile teams evaluating KMP start with a library publishing model. KMP module libraries are written, versioned, and "consumed" by the apps. The classic approach is to build and publish binary dependencies. In 2024, with KMP at stable and gaining significant traction, we no longer recommend this approach. It makes an inherently imbalanced iOS developer experience worse. Share Kotlin source instead. ## GitPortal: Bidirectional, Eventual Code Sharing for KMP Teams DevFeed: [GitPortal: Bidirectional, Eventual Code Sharing for KMP Teams]() Original publisher: [Read original article]() Published: 2024-06-26T00:00:00Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [multiplatform](), [Mobile](), [Code](), [repo]() Tags: [adopting](), [architecture](), [code-sharing](), [git](), [kmp](), [mobile](), [repo]() ### AI overview This introductory article explains why the default single-repository KMP setup can be difficult for native mobile teams whose Android and iOS specialists work independently. It introduces GitPortal's bidirectional mode as an approach for sharing KMP logic while keeping native app development workflows separate. ### Source excerpt For teams scaling KMP, versioned libraries are inefficient. Merging app code and KMP code into a single repo may be impractical, and introduces its own issues. GitPortal allows bidirectional, eventual code sharing. ## The Risks of WebAssembly DevFeed: [The Risks of WebAssembly]() Original publisher: [Read original article]() Author: Matt Butcher Published: 2022-09-06T17:46:35Z Content type: opinion Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [WebAssembly]() Tags: [adopting](), [post](), [webassembly]() ### AI overview The article discusses four risks to consider when adopting WebAssembly, noting that the technology is still relatively new. ### Source excerpt WebAssembly is a new enough technology that there are still several risks to consider when adopting. In this post, we cover four such risks. ## JetBrains' first Kotlin Multiplatform survey | #TLTouchPoints - Touchlab DevFeed: [JetBrains' first Kotlin Multiplatform survey | #TLTouchPoints - Touchlab]() Original publisher: [Read original article]() Published: 2021-02-24T18:51:11Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [jetbrains]() Tags: [adopting](), [insights](), [kotlin](), [kotlin-multiplatform](), [management](), [results](), [survey](), [touchlabshare]() ### AI overview A Touchlab #TLTouchPoints episode summarizes key insights from JetBrains' first Kotlin Multiplatform survey and discusses implications for management considering KMP. ### Source excerpt JetBrains recently released the first ever Kotlin Multiplatform survey. In this episode of #TLTouchPoints Justin summarizes the key insights from the results and implications for management considering KMP. ## Kotlin 1.4 Online Event - Day 1 Recap - Touchlab DevFeed: [Kotlin 1.4 Online Event - Day 1 Recap - Touchlab]() Original publisher: [Read original article]() Published: 2020-10-13T00:11:29Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [kotlin multiplatform mobile](), [Kotlin Multiplatform](), [Kotlin](), [jetbrains](), [Mobile](), [Development]() Tags: [adopting](), [engineering](), [event](), [kmm](), [kotlin](), [kotlin-multiplatform](), [recap](), [touchlabshare]() ### AI overview A video recap of Day 1 of the Kotlin 1.4 online event, covering KMM announcements and development. It notes Kotlin 1.4's focus on quality and performance and targets engineering managers considering KMM adoption. ### Source excerpt The following video is a recap of Day 1 KMM announcements and development from the Kotlin 1.4 event. This video is intended for managers interested in KMM. ## Touchlab's Perspective on VMware Adopting Kotlin Multiplatform DevFeed: [Touchlab's Perspective on VMware Adopting Kotlin Multiplatform]() Original publisher: [Read original article]() Published: 2019-11-25T16:42:50Z Content type: opinion Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [multiplatform](), [Kotlin](), [jetbrains]() Tags: [adopting](), [code-sharing](), [kotlin](), [kotlin-multiplatform](), [multiplatform](), [press](), [thoughts]() ### AI overview Touchlab comments on VMware's adoption of Kotlin Multiplatform, discussing its experimental status, limited library support, native-library interoperability, and the implications for adoption risk. ### Source excerpt VMWare was searching for a multiplatform solution and after careful consideration, they endorsed Kotlin Multiplatform. Touchlab shares its thoughts. ## NIST Opens Comments on Draft Secure Software Development Framework DevFeed: [NIST Opens Comments on Draft Secure Software Development Framework]() Original publisher: [Read original article]() Author: Adam Published: 2019-07-11T00:00:00Z Content type: article Language: en Sources: [Shostack & Friends Blog]() Topics: [Vulnerabilities](), [Application Security](), [Software Engineering]() Tags: [adopting](), [framework](), [nist](), [open](), [risk](), [secure-software](), [ssdf](), [vulnerabilities]() ### AI overview NIST has released a draft Secure Software Development Framework (SSDF) for public comment, with comments accepted through August 5. ### Source excerpt Mitigating the Risk of Software Vulnerabilities by Adopting a Secure Software Development Framework (SSDF) from NIST is open for comment. ## Bringing the 201 Created team to Addepar DevFeed: [Bringing the 201 Created team to Addepar]() Original publisher: [Read original article]() Author: Alex Navasardyan Published: 2019-01-28T18:35:05Z Content type: news Language: en Sources: [Addepar]() Topics: [Ember](), [Tech Debt](), [Front end](), [code productivity](), [web applications](), [JavaScript]() Tags: [adopting](), [announce](), [ember](), [front-end](), [javascript](), [productivity](), [team](), [tech-debt]() ### AI overview Addepar announces that the team from 201 Created, a JavaScript consulting firm, will join the company as full-time staff. The team will help modernize Addepar's older Ember.js web application codebase and form the core of a new internal group focused on web technology improvements, best practices, and front-end developer productivity. ### Source excerpt I'm excited to announce that the team at 201 Created, a Javascript consulting firm, is joining Addepar in February. Seven months ago we asked them to help modernize Addepar's web application codebase, and now we're welcoming Matthew Beale, Cory Forsyth, Jonathan Jackson, and Kevin Pfefferle as full time staff. Addepar's original product was a Java Swing application. Seven years ago we started rewriting that application onto the web platform with Ember.js at its core. We were motivated by the promise of faster feature development, an ability to improve usage analytics, to quicken the app's loading speed, automate testing, and to provide better security to our users. When the codebase was new, modern, and smaller those promises were delivered on. But after years of a hard focus on features to ensure Addepar's adoption by the market we've accrued some tech debt. Addepar's main codebase runs on an older, unsupported version of Ember.js making it difficult to leverage the latest productivity improvements enjoyed by the wider Ember.js (and web development) community. Working with out of date software makes documentation and education a constant challenge for our front-end developers. To maintain the benefits of Addepar's original web refactor on what is now a much older and mature codebase, we're forming a new internal team at Addepar. This team will focus on practical web technology improvements, adopting best practices, and accelerating front-end developer productivity. We're looking forward to having 201 Created's team form the core of this group, and to leveraging their technical knowledge and background in pairing and training. We're excited to welcome Matthew, Cory, Jonathan, and Kevin to our team at Addepar! You'll find them and other Addepar staff at EmberConf 2019. Read more on this change at the 201 Created blog. Interested in working with us at Addepar? Visit addepar.com/careers. Bringing the 201 Created team to Addepar was originally published in Build@Addepar ## Frontend Dev Best Practices for 2017 DevFeed: [Frontend Dev Best Practices for 2017]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2017-01-03T21:14:00Z Content type: article Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Front end](), [Development](), [Web](), [Boilerplate](), [Chrome]() Tags: [2017](), [adopting](), [best](), [best-practices](), [chrome](), [consider](), [developer](), [exploring](), [frontend](), [google](), [https](), [insights](), [practices](), [search](), [serp](), [web](), [you-re]() ### AI overview A 2017 guide for frontend web developers recommends adopting one new technology, methodology, or design pattern in each project. It also recommends deploying new websites with HTTPS and HTTP/2. ### Source excerpt If you're a frontend web developer, here are some best practices you might consider exploring or adopting in 2017