Embedded is a website devoted to the concerns of professional engineers developing embedded systems -- the software, firmware, and hardware – and integrating them and testing. We publish articles and blogs that explain all techniques, methods, and algorithms related to embedded systems. Our goal is to advance the state of the art for our readers, making their lives easier and simultaneously improving their productivity. To that end, we need your help. We are looking for embedded systems engineers and developers who will share their experience with our site users.
We define an embedded system as one based on a microcontroller or microprocessor or other IC that has a dedicated function and is part of a larger system. The range of such systems is quite large and Embedded regularly publishes articles on a variety of subjects. Embedded systems range from 8-bit microcontrollers to 64-bit RISC machines, with software ranging from simple data logging to sophisticated applications using real-time operating systems and multiple processors. Typically, an embedded system is housed on a single microprocessor board with the programs stored in ROM. Virtually all appliances that have a digital interface -- watches, microwaves, cars, airplanes, medical devices, robots -- use embedded systems. Some embedded systems include an operating system, but many are so specialized that the entire logic can be implemented as a single program.
In a similar vein, we consider Embedded a website for professionals, not for hobbyists or academics. Our readers prefer the proven technique to the theoretical novelty. We won’t refuse to deal with new or controversial topics, but your article should demonstrate a practical solution.
Types of articles and content we accept
Embedded primarily focuses on the “how-to” in development, with occasional forays into the “why-to” as well. The vast majority of the articles in the website discuss various techniques and methods for improved development. While the topic discussion and examples might use specific processors, hardware, or software, the underlying lessons of the article should be applicable to other target configurations.
Most of our articles are contributed by embedded systems developers and in some cases, vendor or industry experts. Embedded.com has evolved from a solely developer-written site to a community where both embedded systems developers and engineers working for tool or hardware vendors write content and interact in forums. Although our community now includes some technical representatives of vendors, we serve the embedded systems developer first and foremost. Our editorial staff uses the same editorial standards and process to review and approve all contributed content on the site. If you see the article on the site, an editor deems the article as useful to our readers. We promise to clearly identify what company an author represents.
We post these types of content on Embedded:
Opportunities for embedded systems developers, engineers, designers, and managers:
- Long-form development articles: These tutorials instruct colleagues how to do achieve a proven development technique, improve performance of a system or a team, and avoid pitfalls. Written by embedded systems developers for other embedded systems developers, we put these articles into at least one of 12 of our Development Centers, on our home page, and in our newsletters. Contact Susan Rambo at email@example.com.
- Blogs: Commentary written by expert embedded systems developers. Are you the next embedded systems expert? Do you want to write a blog? You can pitch your idea to Susan Rambo at firstname.lastname@example.org.
- Source code: Often submitted with a how-to-develop article, you may also submit a standalone code to us that you are willing to share for free with other developers. Contact Susan Rambo at email@example.com.
- Video: We’ll be happy to look at a video you’ve made of a project you are working on or a day in the life of your team. If an editor likes it, we’d love to post it on our web site in the appropriate Development Center. Contact Susan Rambo at firstname.lastname@example.org for details.
- Product reviews: Want to review a product that you use, a new version of a product? Contact email@example.com.
- Book reviews: Want to review a book? Contact firstname.lastname@example.org.
Opportunities for vendors, marketeers, book publishers, press reps, industry groups:
- Long-form articles: Contact Bernard Cole, our site editor, at email@example.com. These articles follow the same process and standards as a development article submitted by developers (see above). Click here for detailed information on submitting an article. Topics here include general tutorials on a proven software technique, how to use an up-and-coming technology, and standards updates and what to expect. Send your ideas to our site editor.
- Events: Submit your industry event for posting on our events calendar. Email the details to events calendar editor at firstname.lastname@example.org.
- Competitions: We keep track of competitions our readers might find interesting and fun. We also work with vendors who want to create a simple competition and give away a free dev kit or samples to our readers. Contact editor email@example.com for more information.
- Video: Vendor-sponsored videos can be very popular on our site. The editors may embed interesting vendor videos in their blogs or collections and may plug a video they like in our newsletters, but we don’t mix vendor videos advertise products in the editorial playlist on our video players. Your videos, however, can be placed prominently on our home page in the vendor sponsored play list, right next to the editorial playlist. Talk to our sales department about posting your video on our vendor playlist.
- New product announcements: Send press releases to editors Bernard Cole at firstname.lastname@example.org, Susan Rambo at email@example.com, and Toni McConnel at firstname.lastname@example.org.
- Industry announcements: Send press releases to Susan Rambo at email@example.com, Bernard Cole at firstname.lastname@example.org, and Susan Rambo at email@example.com.
- Book chapters: We post book chapters from newly published books in exchange for linking to the publisher’s information page or to the book page on Amazon.com. Book chapters get a mention in our newsletters and are treated as development articles, so they are placed in our top carousel on home page (and may sit there for as long as a month) as well as being featured on relevant Development Center home pages. Send to Bernard Cole at firstname.lastname@example.org.
Please note: Webinars, technical papers, and courses are often paid, sponsored content from TechOnline library. However, our editors will often highlight useful content from TechOnline.