Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users

Dashboard
Notifications
Mark all as read
Meta

Welcome to Electrical Engineering!

+12
−0

Welcome to the Codidact site for Electrical Engineering! We're glad you're here and we're excited to see what you will build. This community is starting "from scratch", without importing Q&A from other sites, so your community can set its own direction. Please ask questions about electrical engineering in the Q&A category and use this Meta category to discuss site policies, scope, customizations, and other matters. You can report bugs and ask for support here, too.

If you already have an account on another Codidact site, click "sign in" and use the same email address and password -- you're already in the system and don't need to create a new account. If you're new to Codidact, click "sign up" to create an account for yourself.

This site is running on beta software that will eventually become Codidact. We started with a Q&A platform that already existed, and over the coming weeks, we will be evolving this software toward the feature set we've identified for the first official release of Codidact. This means some things will change (mostly things will be added), but the core -- a community built around people working together to ask and answer questions -- will not change. You can read more about the vision for the platform and the features for the first release.

There is a reputation system here for now, and there are a few rep-based privileges, but it's kind of like a private beta at SE; everybody can do most things, so be careful. I believe deletion requires only one vote and auditing is limited. We don't have many moderation tools yet, but we do have flags. Be nice and be careful please. If you run into problems or have questions, post here on meta. Reputation will eventually be replaced by more specific stats (like how many answers you've posted and roughly their total score), and a system of trust levels will grant privileges based on your activity on the site.

We don't have on-site chat yet, but there is a Discord server for Codidact communities. Pop into the "access-management" channel and check off the communities you want to see chat rooms for. (This is so you don't have to wade through rooms for sites you're not interested in every time you visit.)

Welcome aboard!


This site was proposed on Codidact Meta.

Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

3 comments

"This community is starting "from scratch", without importing Q&A from other sites". So does that mean that questions taken from other Q&A sites are not allowed to be posted here? For example, can I repost here (at the main site) a question I previously posted at Electrical Engineering Stack Exchange with no answer yet? Joel Reyes Noche‭ about 1 year ago

@JoelReyes please do feel free to bring your questions here from there -- let's try to get you some answers. I just meant that we didn't do any bulk imports like has been done on some other Codidact sites. Monica Cellio‭ about 1 year ago

Okay, thank you. Joel Reyes Noche‭ about 1 year ago

2 answers

+5
−0

Welcome and thanks, Monica. It might be good to set some basic expectations in terms of schematic diagram rather than word salad, sharp photos in case of identification questions, and inclusion of any and all relevant code in the case of firmware questions. In particular LTspice simulation questions should include the .asc file and any models that are not in the standard distribution (these are all human-readable ASCII).

Can the short list of "posting tips" be customized to the site?

Why does this post require moderator attention?
You might want to add some details to your flag.

4 comments

The posting tips can be configured per-site and per-category. Unfortunately, though, there is no mod/admin interface for it yet, so we'd need to enter it manually into the database. luap42 😷‭ about 1 year ago

Yes, I'm working on documentation about the site. Even though the site framework has been set up, I don't consider it ready yet. This is mostly about lacking documentation. You can see where I started this with "Intro to this site" under HELP. I don't want to advertise the site until all this is in place. This may take a few days to a week. My day job is heating up. Olin Lathrop‭ about 1 year ago

It sounds like we'll want customized posting tips that link to more-detailed help. Moderators can create the help and, as luap42 said, we can edit the posting tips for you when you're ready. Monica Cellio‭ about 1 year ago

@Monica: Maybe a fourth posting tip that links to https://electrical.codidact.com/help/asking "for more detail" or something like that? Olin Lathrop‭ about 1 year ago

+2
−0

Thank you Monica!

While the technological world is evolving more towards software solutions, it's also important to think about what makes software tick, and that would be with the help of hardware. This new website should encourage those who are, but not limited to people who are, engineers, professionals, students, hobbyists, and those who are generally interested in the world of electricity.


With this website, we can focus on the following topics in electrical engineering:

  • Electromagnetism
  • Electrical physical laws of nature
  • Control engineering
  • Circuit design
  • Circuit analysis
  • Application of electrical components
  • Root cause analysis and troubleshooting
  • Power generation
  • Transmission systems
  • Signal processing
  • Electrical instrumentation and measurements
  • Telecommunication systems
  • Electrical properties of material science
  • Electro-optics
  • Computer engineering
  • Solid-state physics
  • Electromechanics
  • Numerical characteristics for electrical problems
  • Fabrication of electrical devices
  • Coding for embedded systems and control systems
  • Coding for electrical and/or control design
  • Electrical codes and standards
  • Electrical vehicles (future topic)
  • Quantum computing (future topic)
  • Advanced research topics in electrical/electronic/computer engineering
  • History of electrical devices and sciences and how they work.

To preserve proper usage of this of this website, some topics that would not be considered useful here include:

  • General electronic part functionality, i.e. "How does this part work?" or "Will this work for what I'm doing?" or "What if I do XYZ?" However, this may be different when understanding any history of technologies. If someone wishes to ask about the history of particular technologies, they must be very specific on what they wish to know.
  • General coding questions, i.e. "How do I write my code to do XYZ?" or "Will this work for what I'm doing?" or "What does this keyword mean?"
  • Recommendations for products, i.e. "Is there an alternative/a newer product that provides the same functionality?" or "Is there a product that does XYZ?" This includes software recommendations for hardware design.
  • Ideas for projects to work on.
  • Shopping websites or stores, i.e. "Where can I go to purchase XYZ?" or "What website do you recommend for people in [a specific country]?" or "Have you all had experience with Company A's products and/or customer support?"
  • Homework/Work/Assignment/General curiosity questions, i.e. "I'm trying to solve for XYZ." or "I've been assigned to do XYZ." or "I'm trying to learn how to do XYZ so that I can understand it better."
  • Questions with little to no effort. This can be seen as too broad of a question.
  • Repairing questions, i.e. "I broke XYZ, how can I put it back on there?" or "Where can I find a replacement?" or "Is there an alternative solution to this broken part?" ... But this may be different from something like, "I'm seeing this behavior, how can I compensate for that?"
  • Part identification, i.e. "I found this in my old computer, what is it?" or "What does this marking mean on my circuit board?"
  • Step-by-step instructions on how to do something. This website should help to improve or teach people how to do something, not provide a solution.
  • Providing troubleshooting from external reference resources such as websites, textbooks, videos, etc. To clarify, users should not ask how to do something they saw elsewhere. This is different from asking questions about interpretation of content in a datasheet or application note from the official manufacturer of that product.
  • Educational resources where they can learn to do XYZ or "get started" or learn more about a particular topic.
  • Usage of software tools, i.e. "Where can I find the option to do XYZ?" All software has online resources on what the user wishes to do.
  • Anything else that is blatantly not about electrical, electronics, computer, or embedded system topics.
  • Personal life advise on how to pursue a career in electrical/electronic/computer engineering including their job or education or general interest. This also includes involvement with organizations such as IEEE, IEC,
  • Ambiguous topics that can be somewhat related to electrical/electronic/computer engineering such as mechanical systems, thermal and airflow design, present (i.e. right now, modern day) engineering economics, biotechnology and biophysics, electrical behavior outside of Earth, acoustical physics, etc.
  • Asking about technologies that do not have any documentation or have documentations that cannot be easily found online or requires a paywall or talking with sales of a particular product.
  • Asking for assistance with their research including where they can find particular information on a topic or asking for our perspective of their research topic.

The reason why these topics would not contribute to this website is because we want to preserve information that can be used in the future. Technology always changes and becomes quickly outdated.

Why does this post require moderator attention?
You might want to add some details to your flag.

9 comments

This looks like a good, thorough explanation of your scope. I see y'all are already writing help topics; once you have consensus I encourage you to create one based on this post. Monica Cellio‭ about 1 year ago

Oh, also: you know that text that's at the top of the question list in each category? We can edit that and markdown is supported. I took the text for the Q&A category from the site proposal, but if y'all want changes, let us know. (Best to do that in a new meta post where we'll be sure to see it.) Monica Cellio‭ about 1 year ago

@Monica: I think the short text is good. That's not the place for a detailed list like this. Olin Lathrop‭ about 1 year ago

@OlinLathrop right, we wouldn't want that much detail in the page heading. We could, however, add a link to a help topic on this subject if you want. Just letting you know you can request adjustments to that summary text. Monica Cellio‭ about 1 year ago

@Monica: I'd like a link to https://electrical.codidact.com/help/intro with something like "Read this before posting" from the main Q&A page. Maybe the "this" is the clickable link? You can decide the details, but there should be no excuse for not having known that page should have been read before posting. Olin Lathrop‭ about 1 year ago

Show 4 more comments

Sign up to answer this question »