We'd never keep up without curated reading lists that help us build RSS feeds ... especially in rapidly evolving industries with lots of investment driving R&D and new theoretical work.
A rapidly developing research and development space such as eGPUs/eTPUs connectivity illustrates why. But, more generally, it is important to curate repositories of lists of AWESOME blogs and online publications by independent thinkerers, industry experts and research institutions ... by following these curated lists, or the abstracts from linked RSS feeds, one is better able to an eye on key things.
So it's not JUST researchers/labs involved that developing as well as the conferences and workshops focused on HPC, cloud computing, and server technologies, as these often serve as a place for new ideas in cutting-edge research and development in eGPU/eTPU connectivity to emerge ... we ALSO continue to learn from Archetypal Repository which laid the foundation for the broader archetypal example of listification in the Awesome Lists of Awesome Lists.
We will focus this AWESOME lists on various patterns, methodologies, practices and tools used in the development of asynchronous workflows ... we are our own most demanding customer for what is a particularly recursive topic, since we are all about using asynchronous workflows as we dogfood the asynchronous workflows that we will use to dogfood new asynchronous workflows.
Gordon Firemark helps independent artists, writers, producers, directors and knowledge workers in cyberspace achieve their dreams in the fields of theater, film, television, new media, intellectual property, software development and professional services contracting. Firemark is the producer and host of Entertainment Law Update, a podcast for artists and professionals in the entertainment and intellectual property industries; he's also the author of The Podcast, Blog and New Media Producer's Legal Survival Guide.... as of 2024, your asynchronous workflow will need to includes things like US federal compliance reporting ... for you and the independent contractors you work with.
These kinds of PREDICTABLE asynchronous workflow disciplines will be particularly important for the development of software and any kind of design or intellectual property ... if you work with other professionals asynchronously, everyone involved is going to NEED to understand their colleague's workflows. This does not mean that you direct them or that you will be directed by them as if you were an onsite worker bee housed somewhere in cubefarm or off in a work trailer in the parking lot. The point is everyone involved NEEDS to understand each other's workflows well enough to be able to collaborate as if you were sitting right there in person. This means things VPNs, information security, reliable and secure file sharing, and proficiencies with things like version control tools like Git that enable you to work asynchronously in some semblence of a coherent, predictable fashion, ie just emailing attachments back and forth like it's the 2000s is NOT close to being a professional asynchronous workFLOW ... that can be fine for one or two or a handful exchanges while you're both getting things set up, but as a regular, predictable, efficient workflow, doing that kind of backward crap is just some sort of pathetic electronic shit-shuffle badminten game, ie professionals do not play games with their workflows unless they're the kind of child professionals who need to be onsite in order to be supervised and chaperoned.
Developers work on independent branches for specific features, merging them into the main branch once complete. This fosters collaboration while minimizing conflict.
Beyond using GitHub Projects ... what are some OPEN SOURCE ways that teams visualize and track individual tasks on virtual boards, facilitating clear communication and ownership.
SHIFT your thinking LEFT ... think of observability engineering [including security aspects of testing a user's environment for intruders] as being akin to hardware development, rather than an afterthought ...incorporate a DFT strategy into the architecture of your workflow ... consider adapting ideas from hardware development into your software development ... think about things such as hierarchical DFT with Memory Built-In Self Test (MBIST), IJTAG/TAP and Hi-Speed IO, traceable requirements from fundamental DFT logic, with pre-silicon verification to Co-work with test engineers post silicon ... shift the testing left, and make copilot the design process by understanding how boundary scan, scan chains, DFT Compression, Logic Built-In Self Test (BIST), Test Access Point (TAP) controller, Clock Control block, and other DFT IP blocks are used in hardware. Design in the observability and controllability of the design to enable testability; consider why it's so important to insert and hook up MBIST logic including test collar around memories, MBIST controllers, eFuse logic and connect to core and TAP interfaces. Document DFT architecture and test sequences, including boot-up sequence associated with test pins. Make it almost effortless to test the design by using the DFT architecture to control the design and test sequences; complete all Test Design Rule Checks (TDRC) and Design changes to fix TDRC violations to achieve high test quality which can support to the traceability and analytics used to improve customer use and interactivity.
Developers asynchronously review each other's code after pull requests, ensuring quality and knowledge sharing ... not just tools like Gerrit, but the best practices for Gerrit.
Organize tasks, assign priorities, and track progress asynchronously through platforms like Jira or Asana.
Tools like Notion or Confluence enable team members to contribute to shared documents and wikis at their own pace.
Share concise summaries and action items from meetings via email or internal platforms, ensuring information accessibility.
Beyond utilizing best practices for platforms like Dropbox or Google Workspace, there's a lot of Git and Mercurial to cover.
Tools like Figma or Adobe XD allow asynchronous feedback on design mockups and prototypes, promoting iterative improvement.
Slack, Discord, or Telegram enable quick updates, file sharing, and discussions even when team members are offline.
Regardless of the workflow, establishing clear expectations, deadlines, and communication channels is crucial for asynchronous success.
Sharing project progress, decisions, and rationale through documentation enables everyone to stay informed even when working asynchronously.
Leverage appropriate tools and platforms to facilitate smoother asynchronous collaboration and information sharing.