I see all these tools for the past few years claiming...

"build an app without writing code"

Great, if you want to build a prototype and then try to find a technical co-founder who can actually build something.

Otherwise, none of us need another shitty cookie-cutter app.

There is a 0% chance you can build anything that will scale without writing some code. Your best case scenario is you sell it to some sucker who doesn't understand that what they are buying is garbage.

I give those folks 3 options...

1. Find a technical co-founder
2. Learn to build software
3. Fuck off

Thinking you can build a software company without building actual quality software if fucking moronic.

Of course, that won't stop the thousands of business grads each year from trying and saying...

"I have such a great idea, I just need someone to build it"

Let's get things straight. You have nothing. NOTHING! You idea is worthless without execution.

I don't care what idea you have. I am not joining your "startup" as a technical co-founder. I too wish I could go to the store and buy bread with fucking equity

# Retrospective as Backend engineer

Once upon a time, I was rejected by a startup who tries to snag me from another company that I was working with.
They are looking for Senior / Supervisor level backend engineer and my profile looks like a fit for them.
So they contacted me, arranged a technical test, system design test, and interview with their lead backend engineer who also happens to be co-founder of the startup.

## The Interview

As usual, they asked me what are my contribution to previous workplace.
I answered them with achievements that I think are the best for each company that I worked with, and how to technologically achieve them.

One of it includes designing and implementing a `CQRS+ES` system in the backend.
With complete capability of what I `brag` as `Time Machine` through replaying event.

## The Rejection

And of course I was rejected by the startup, maybe specifically by the co-founder. As I asked around on the reason of rejection from an insider.

They insisted I am a guy who overengineer thing that are not needed, by doing `CQRS+ES`, and only suitable for RND, non-production stuffs.

Nobody needs that kind of `Time Machine`.

## Ironically

After switching jobs (to another company), becoming fullstack developer, learning about react and redux.
I can reflect back on this past experience and say this:

The same company that says `CQRS+ES` is an over engineering, also uses `React+Redux`.
Never did they realize the concept behind `React+Redux` is very similar to `CQRS+ES`.

- Separation of concern
- CQRS: `Command` is separated from `Query`
- Redux: Side effect / `Action` in `Thunk` separated from the presentation
- Managing State of Application
- ES: Through sequence of `Event` produced by `Command`
- Redux: Through action data produced / dispatched by `Action`
- Replayability
- ES: Through replaying `Event` into the `Applier`
- Redux: Through replay `Action` which trigger dispatch to `Reducer`

---

The same company that says `CQRS` is an over engineering also uses `ElasticSearch+MySQL`.
Never did they realize they are separating `WRITE` database into `MySQL` as their `Single Source Of Truth`, and `READ` database into `ElasticSearch` is also inline with `CQRS` principle.

## Value as Backend Engineer

It's a sad days as Backend Engineer these days. At least in the country I live in.
Seems like being a backend engineer is often under-appreciated.
Company (or people) seems to think of backend engineer is the guy who ONLY makes `CRUD` API endpoint to database.

- I've heard from Fullstack engineer who comes from React background complains about Backend engineers have it easy by only doing CRUD without having to worry about application.
- The same guy fails when given task in Backend to make a simple round-robin ticketing system.
- I've seen company who only hires Fullstack engineer with strong Frontend experience, fails to have basic understanding of how SQL Transaction and Connection Pool works.
- I've seen company Fullstack engineer relies on ORM to do super complex query instead of writing proper SQL, and prefer to translate SQL into ORM query language.
- I've seen company Fullstack engineer with strong React background brags about Uncle Bob clean code but fail to know on how to do basic dependency injection.
- I've heard company who made webapp criticize my way of handling `session` through http secure cookie. Saying it's a bad practice and better to use local storage. Despite my argument of `secure` in the cookie and ability to control cookie via backend.

Wondering who all looking for technical co-founder?

Non technical Co-founder comes up with some batshit crazy idea and says it’s Agile because he thinks that means you’re not allowed to argue with it.

Dumb people are dumb.

Any technical cofounders here? I've been offered to be a technical co-founder for a new venture. This is a venture that has the same founding team as the startup I'm working with for last 3 years or so. The current venture may be acquired in the near future with the founding team exiting.

Now my question (s) are these:
1. I know the team. We're friendly. But until now the relationship has been that of an employer-employee. What all should i consider before taking this up?
2. Since founders generally take up salaries only what is required for them to sustain. It would mean a financial cut for me too. So I'm stuck in the dilemma of moving towards an entrepreneurial route vs if it fails and I've to work again i may have to start off with a lower salary in the future.

I'm a risk taker (some call it seeker) when it comes to that. Looking forward for some helpful suggestions.

Hello!. I have a little tech app idea I'll love to startup. I made an educated guess that my target users are mostly on the android platform. At least 70-80%.Now I don't have funds to get a development team and I want to keep the expenses to the barest minimum. I have a little tech background. I have, used html, css, c# in the past. I always hated Java in school. But it seems I have to embrace it or Kotlin for the development of the app. I want to be able to build at least the MVP and try to gain traction. I am also thinking about cross platform options to cater for both Android and the few iOS users we may have. React Native and Flutter comes to mind. I also think I can get someone highly technical than myself as a co-founder to help. I will appreciate it if you can drop your 2 cents.