Introduction

Today, I’m joined by Ansel, Manager of Data Analytics at Thermo Fisher Scientific. And with his help, he coaches me on the importance of data, with a stronger emphasis on its value for your business.

---

Highlighted Topics

1. During the creation of software (new/existing) when do you usually get consulted for your expertise?
2. During the creation of software (new/existing) when do you think you should be consulted?
3. What are the types of data sets, KPIs or metrics that you’d like the software developer to be aware of?
4. What problems do you find to be commonplace when interfacing with development teams?
5. What would be the most important topic to add to existing software development curriculum – Analytics or Agile/Collaboration Training?
6. What core languages are you using at the moment (e.g. Python)?
7. When you’re in the trenches of analytics, what do you find to be the most cumbersome part of doing the job on hand?
8. What advice could you provide new developers who are ready to strike on their first opportunity?
9. What advice could you provide new data scientists/analysts who are ready to strike on their first opportunity?

---

Thanks again for listening in. Remember, I’m here to foster innovation through conversation. So if you’d like to continue this discussion or any topics previously discussed, join me at San Diego Tech Hub and go head first into the AllWebSD Group. It’s totally free. Just visit this link or click San Diego Tech Hub on the footer of AllWebSD.com. Thanks and Aloha!

Introduction

Today, I’m joined by Justin, Senior Software Engineer at ParTech. And with his help, he walks me through a high-level explanation (by way of Italian food) of what a MicroService is!

---

Highlighted Topics

• What were you doing before getting into BackEnd professionally?
• Going from a Monolithic Architecture to MicroServices – tell me what that was like?
• My monolithic code already works – why do we need to do this?
• How do you have narratives, conversations or presentations in regards to saving money?
• What on Earth is a MicroService?
• Are you still supporting any backwards compatibility?
• In your experience, what kind of gotchas are you looking at when it comes to implementing?
• From an individual contributor perspective, has there ever been a tipping point in your MicroServices journey where you just wanted to pull your hair out?
• Outside of MicroServices, how are you doing in this pandemic world?

---

Thanks again for listening in. Remember, I’m here to foster innovation through conversation. So if you’d like to continue this discussion or any topics previously discussed, join me at San Diego Tech Hub and go head first into the AllWebSD Group. It’s totally free. Just visit this link or click San Diego Tech Hub on the footer of AllWebSD.com. Thanks and Aloha!

Introduction

It’s always fun to stumble onto an easter egg. But it’s even more fun when they’re Chuck Norris easter eggs. And my Automation Engineer left quite a few on our Jenkins server.

So without further ado, I’ll leave you with some amusement with a bit of an ASMR twist. Let’s begin!

No statement can catch the ChuckNorrisException.

When a bug sees Chuck Norris, it flees screaming in terror, and then immediately self-destructs to avoid being roundhouse-kicked.

Chuck Norris rewrote the Google search engine from scratch.

“It works on my machine” always holds true for Chuck Norris.

There is no need to try catching Chuck Norris’ exceptions for recovery; every single throw he does is fatal.

Chuck Norris doesn’t need an OS.

All browsers support the hex definitions #chuck and #norris for the colors black and blue.

You don’t disable the Chuck Norris plug-in, it disables you.

Chuck Norris doesn’t need to know about class factory pattern. He can instantiate interfaces.

Chuck Norris doesn’t program with a keyboard. He stares the computer down until it does what he wants.

Chuck Norris can compile syntax errors.

Chuck Norris’s beard can type 140 wpm.

Chuck Norris doesn’t bug hunt, as that signifies a probability of failure. He goes bug killing.

When Chuck Norris presses Ctrl+Alt+Delete, worldwide computers restart is initiated.

When Chuck Norris gives a method an argument, the method loses.

The only pattern Chuck Norris knows is God Object.

---

Thanks again for listening in. Remember, I’m here to foster innovation through conversation. So if you’d like to continue this discussion or any topics previously discussed, join me at San Diego Tech Hub and go head first into the AllWebSD Group. It’s totally free. Just visit this link or click San Diego Tech Hub on the footer of AllWebSD.com. Thanks and Aloha!