I'd never bother suggesting it though:
- no one likes being told they're small when they think they're big
- it's bad for devs careers (Resume-Driven Development)
- as TFA points out - it's not what FAANG are doing so I'd lack legitimacy
I'd never bother suggesting it though:
- no one likes being told they're small when they think they're big
- it's bad for devs careers (Resume-Driven Development)
- as TFA points out - it's not what FAANG are doing so I'd lack legitimacy
Most developer's resumes would be vastly enhanced by delivering a lean, technically successful product to end users, or 5.
A lot of developers think playing with cool technology makes them better developers for some reason.
Which isn't true.
What makes them better developers is knowing what that technology does, and choosing the appropriate solution.
And building consensus, managing personalities and driving execution. By being a reliable, high quality human being.
Which is very different to knowing how to operate the API for that solution.
It worked poorly, took months to build, and lost data. I implemented a python script that read from twitter firehose and wrote directly to redshift. It was about 50 lines long and did the same thing, and I deployed it to two existing prod servers that were not network bound.
There was a few more cases like the on-shore database identity reconciliation being inefficient, so the company wanted to leverage cloud auto scaling. Well, if you have an exponential time algorithm and you put it into the cloud, it will still be exponential time and cloud auto-scaling will be extremely expensive, and also introduce latency between distributed system components, and indeed it was. The offshore teams initial logic was only that, cloud is auto scaling so can accommodate any performance the business logic needed.
Sometimes people just view tech/cloud as lego blocks to glue together, based on the product sheet marketing, and do not have enough basic understanding of computer science to understand performance, or understand what a simple solution would look like
It's next to impossible to hold an engineering team together to even KTLO if you don't have some project which grow's their careers.
So one might not get in due to lacking .NET skills, but the other enterprise architecture and soft skills will be just as relevant.
Then it is up to the person to sell themselves.
Source, I have been jumping across .NET, Java, C++, native and Web for almost 30 years now.
Couldn't you... just fib? And learn it in a weekend?
“Grinding LeetCode” (tm r/cscareerquestions) doesn’t make you a better developer. But it does get you in the top paying companies. Well I didn’t. But that’s a different story.
On the other side of the fence in corp dev where pattern matching is the norm, employers aren’t going to want to hear that you used Sqllite.
I would've sworn it was postgres. Just shows how much attention I pay to anything that isn't business logic
"Sweaty Startups"
- Lawn work
- Accounting/Bookkeeping
- Power washing
- House cleaning
And a single content site monetized by affiliate/ads
When I want to create a new site I ssh in and type:
sudo ee site create yourdomain.com --wp --letsencrypt
And I have a deployed wordpress site and ssl certificate.
Try getting a job as a dev with vanilla JS and SQLite skills, as opposed to React and Microservice skills. What a business needs on a technical level doesn't matter when it comes to finding jobs.
Hand-building a reactive (lowercase r) table with sorting, filtering, etc. that's performant at large data volumes to keep your stack "simple", would be a nightmare to maintain and wouldn't allow other developers to bring prior experience with them when they later have to maintain that code.
This environment would necessitate "reinventing the wheel but so much worse" for anything other than the absolute most trivial applications.