_omnf

I love no code! Wait. Wait. Hear me out... Building software is easy. Changing people's minds is damned near impossible.

As an engineer:

- I'm constantly handed shitty (or a complete lack thereof) requirements from non-technical people. No code lets people figure out that they haven't thought something out nearly as much as they think they have. I no longer am the bearer of bad news.

- I constantly see business people undervalue the design process or skip it all together. No code is making non-technical people realize that they have to plan out before they just throw engineers at a problem.

No code is changing the dialog around this. I see that as a net positive. Of course us software engineers know the problems around no-code - we'll deal with them as we deal with all problems.

Salesforce is essentially a database as a service with some fancy admin panels and prebuilt web interfaces.

The tech is proprietary, and not that fun to work with. [0]

As someone who has worked extensively with Salesforce, the cult like fanbase is annoying. I'll be the first to admit the tech is underwhelming and in many cases nowhere near other modern technology.[1][2][3]

But, I still 100% recommend Salesforce to companies when they ask about it. Why? Data liability. Yes Salesforce is expensive - but you are outsourcing the responsibility of dealing with sensitive data to Salesforce. This is something that they should market more heavily in imo. (at least to sw engineers and CTOs) Realistically many companies are not properly equipped to deal with data, let alone sensitive data. Salesforce may have started out as a CRM, but now it is a solution to that problem. CTO's now have someone to point the finger at if shit hits the fan on an Equifax level. This alone is worth big $$$.

[0] - https://insights.stackoverflow.com/survey/2018#most-loved-dr...

[1] - https://developer.salesforce.com/docs/atlas.en-us.apexcode.m...

[2] - https://developer.salesforce.com/blogs/2018/05/summer18-reth...

[3] - https://developer.salesforce.com/page/Multi_Tenant_Architect...

[4] - https://trust.salesforce.com/en/

At the risk of sounding pompous. I really like my portfolio site: [link redacted]

Why? I built it for myself. Not for what I thought recruiters/employers wanted to see. I simply wanted a place to collect some of the projects I work on. And more importantly one that captured my personality a bit. It's not perfect, I look at it and see a ton things I'd refactor. But it get's people to laugh or start a conversation about something I've done. That to me makes it all worth it.

My $0.02: Don't build a portfolio site because you think you need one, build one if it serves a purpose for you. i.e. learning a new skill, organizing your work, or just having fun. I think the results are much more interesting that way. (Also, don't be afraid to iterate. I think this is the 5th one I've attempted to make)