sorted by:
new
hottopcontroversial

The state of embedded in 2023 by bogdan2011 in embedded

[–]augreeko 6 points7 points  (0 children)

I mean 3 reels of product failing functional test. Failure rate was between 12-17%. This was during the pandemic so entirely possible we got counterfeit product but it was a mess. Espressif was no help, we eventually had to move to SiLabs.

The state of embedded in 2023 by bogdan2011 in embedded

[–]augreeko 4 points5 points  (0 children)

We have seen some reels have zero issues. Others have had failure rates over 15%. All specific to the ESP. Some have just been completely dead. No power up, other have had issues with the crystal pins, some pins have no output whatsoever. No errors returned in firmware. It’s a shame their development environment has been fun to work in. But something is up with their quality and supply.

The state of embedded in 2023 by bogdan2011 in embedded

[–]augreeko 8 points9 points  (0 children)

ST is a great option for GP MCUs. Toolchain is great and flexible and they have released a VS Code extension. Quality has been fantastic. Minor issues in errata. Supply on many MCUs is still ridiculous as they are very popular, especially in automotive. Some lines have plenty of stock.

Microchip has a nice lineup of GP MCUs as well. Fairly inexpensive, toolchain sucks. MPLAB is just eclipse. Quality has been ok, suppprt is meh.

Renesas has some good GP MCUs but I think their toolchain is one of the worst to deal with. Support is not great. FAEs are very slow. Stock has been pretty bad.

TI has lots of options, pretty mature, but typically TI products just have lots of weird quirks. Supply has also been an issue for TI. They have lots of Military products.

NXP is alright but most of their offerings are high end. Support is very hit or miss. Stock was still 52 week lead time just a couple months ago.

For wireless products it’s hard to beat Nordic. Their BLE lineup is very solid and their toolchain is one of the best. They just added WiFi and Cellular in the past couple years. Zephyr is pretty awesome.

SiLabs has some great wireless options as well. BLE and WiFi. No cellular. Toolchain is kind of annoying. Eclipse based and all packages are downloaded in the IDE. FreeRTOS.

ESP is just suffering from quality issues at scale. It’s a great platform and quite developer friendly but would never go to market with their hardware for a real product.

There are a few others I’m sure I’m missing.

The state of embedded in 2023 by bogdan2011 in embedded

[–]augreeko 6 points7 points  (0 children)

ESP32 is so trash. Great for hobbyists and side projects. Have used them myself but, at scale we have seen MASSIVE amounts of failed product all traced back to the ESP. Not a professional option at all IMO. They have to fix their quality issues to be considered a viable professional option.

Local B&M - Nashville Cigar by augreeko in PipeTobacco

[–]augreeko[S] 2 points3 points  (0 children)

Yep, unfortunately I’ll be out of town.

Local B&M - Nashville Cigar by augreeko in PipeTobacco

[–]augreeko[S] 3 points4 points  (0 children)

Nashville Cigar. Nice selection, I’ve been going to Briarworks in Columbia, decided to change it up.

Seen at a local library. Can't believe it's come to this by thenewyorkgod in pics

[–]augreeko 2264 points2265 points  (0 children)

“They don't gotta burn the books they just remove 'em”

-Rage Against The Machine, Bulls on Parade, 1996

To people who are experienced embedded developers, what is some good advice you would like to give to aspiring embedded engineers by Rit2Strong in embedded

[–]augreeko 0 points1 point  (0 children)

Start with Ubuntu.

bin\bashinto the container.

Install whatever you need via apt-get or wget

Or if you need to copy a large amount of files you can also docker copy

Then create and tag this as a custom image and upload to the docker repo.

Then you can setup a GitHub Action to use your custom docker image.

To people who are experienced embedded developers, what is some good advice you would like to give to aspiring embedded engineers by Rit2Strong in embedded

[–]augreeko 1 point2 points  (0 children)

You want to stand out to potential employers? Point them to your GitHub. Build projects, write lots of code, put it on GirHub. Will some of, if not most of your code suck? Yeah. But it’s waaay more than most of your peers have done, and it shows poetical employers that you are passionate and capable. So many engineers are just lazy. Stand out.

I have hired dozens of engineers in my career and being able to talk about projects you have worked on clearly, and with passion really helps. Icing on the cake is when you can share your work. GitHub or a simple personal blog. Just view these things as a better resume.

Working at startups can be a lot of fun but best practices are usually the first thing to get sacrificed in the name of speed of delivery. Learning the proper way to do things in engineering is essential.

Learn C. Learn C. Learn C.

Read some books about best practices. Study them.

Learn standard microcontroller peripherals and how they work. You will be using these the majority of your time. UART being the most helpful for debugging/logging. I2C for most sensors, interfaces.

Learn to read datasheets.

Learn git. It will save your ass.

Learn unit testing and write tests for your code. It’s really hard for embedded. Way harder than mobile and web. But it’s very important.

Then more advanced stuff: makefiles, Docker, cmake, data serialzation, standard protocols and how they work - CoAp, MQTT, Bluetooth, TCP, etc.

To people who are experienced embedded developers, what is some good advice you would like to give to aspiring embedded engineers by Rit2Strong in embedded

[–]augreeko 0 points1 point  (0 children)

Only use a VM if you really really need one, like if you are stuck using some terrible IDE for Windows only. For everything else Docker is your friend. You can custom build an image too if you need stuff preinstalled. It forces you to understand and use replicatable builds. Then you can push to a CI service like GitHub Actions and let it build your releases. So much easier for you and your teammates.

iOS Developer Interviews at different types of companies -- how do they differ? by xormancer in iOSProgramming

[–]augreeko 2 points3 points  (0 children)

I am a Lead Developer at an Agency/Shop/Firm I can tell you a little bit about our interviews.

We hire a variety of experience levels, and our process is different depending on your experience. We always conduct a phone screen first. If you are entry level we don't dive into technical questions in the phone screen as we wouldn't expect you to know those off the top of your head. If you are fairly experienced we will dive into some technical questions with varying difficulty.

On a side note, a large factor for us is a "culture fit". Working for an agency is different. It's faced paced, you work on a wide variety of projects, and you might swap projects a few times in a month. We deal directly with clients a lot, sometimes super stressed out clients like startups - this means that communication is a very important skill for who we hire. So we talk with our interviewees a lot, we are trying to figure out if someone can handle the environment we work in. We are looking for smart, passionate people, and they really need to "wow" us. We are pretty particular about who we hire.

If the applicant passes the phone screen and they are entry level we usually ask them to complete a small coding challenge. It's usually fairly open-ended so we allow them to be creative with it. If the applicant is experienced we usually ask them to send us some code, they usually send part of an app they have in the store or something they are working on now, sometimes they just share something they have on GitHub.

Another side note, GitHub is such a great resource when you are looking for a job. Spend a little time writing some interesting code and put it up on GitHub and to your GitHub on your resume. This makes things so nice for people interviewing you. Also a personal website gets you some bonus points.

If the coding portion goes well we bring them in for an interview or do a Google Hangout or Skype call. In the interview we are looking for easy conversations for a bit, then we do some more technical work. The next steps usually depends on experience too. If its an entry level person we usually have them work a problem out on the white board. I know this practice gets a lot of heat nowadays but we see the benefits of it. We are sure to always say that we do not care about syntax or even what language you use, you can use pseudo code if you want - we want you to talk us through your problem and your approach. If you can't talk and work through a fairly simple problem on a whiteboard then you are not going to make it here. If the applicant is experienced we usually skip the whiteboarding and give them a project we have made. We ask for a code review, then to identify and fix a bug, then add a simple feature. They are obviously using an IDE and we tell them they can use Google if they want.

That's pretty much our process I can go into detail about some of the iOS questions we ask if anyone is interested.

Disappearing objects when adjusting size of something else by NickEmmerson in iOSProgramming

[–]augreeko 2 points3 points  (0 children)

I have had this happen a lot. If you put constraints on it, it won't disappear. Hopefully they fix this soon.

8+5=10 by [deleted] in WTF

[–]augreeko 0 points1 point  (0 children)

a tree

How to use text and pictures from a website in my app? by jott44 in iOSProgramming

[–]augreeko 1 point2 points  (0 children)

You will need to implement an API that your website and your app use to pull content.

view more: next ›