4,021 karma · joined May 11, 2017
Otherwise, if you are in that ambiguous zone regularly, either you are pioneering some super new innovative area, or your organization isn’t very good at software development as a whole.
One org I was at, the product managers constantly complained that developers couldn’t read their minds and automagically “know” all the non functional requirements, validations, etc. They were used to working with super senior devs who knew the space well, and could not adapt to devs who were more junior and also new to the industry vertical.
Work whatever network you have. Build one from past colleagues on LinkedIn if you haven’t. Start applying for remote work. Look for contract gigs if time is that short. Get your CV out there and keep applications flowing to companies.
Using that ruler, go back 6 generations and you are at circa 1900.
I have never understood this POV, but to understand C++ O think you need to grok this key point deeply.
It seems clear that LLM’s are going to be decent as assistants, but the 5x claim is BS and the marketing part of the post. Most of software development isn’t coding, it’s testing and experimenting and bug fixing and refactoring and documenting and interacting with other people and often companies.
If we get to the point where an LLM can get assigned a Jira ticket, make a bug fix, slack the PM for clarification on the ticket, debug the code, write regression tests, etc, then that will be something.
Right now? It’s a much improved Clippy with a very big set of knowledge behind it. When it’s embedded in the SDLC, that will e something. If we ever get there.
“In the same house, in the 1980s, Nonna Fiore once served some English guests lasagna, per my uncle’s request. The lasagna was cooked from frozen, her story goes. Life was busy and, anyway, she had no qualms about serving a supermarket ready meal; people could only dream of such a luxury during the war. None of the guests suspected that she hadn’t made it from scratch and everyone was delighted, her Italian son included. She reminds me of this, then looks up at me and winks”.
Many of our greatest works were built on pools of blood that would not be tolerated today.
Most developers probably do not need data structures, OS, compiler type courses, but instead would benefit from higher level, engineering type courses that reflect modern application design and development.
Note: I am 3 decades out of school, and there have been some moves in this direction I can see from interviewing juniors. But not enough.
Startups you want to see with fairly high tech debt. Tech debt there is a very often a sign of shipped code that is meeting some customer need. You do need to watch out for insane tech debt that may be hard to undo later on (running everything in an ancient proprietary language for example).
Startups with low tech debt often are devs navel gazing without a lot of revenue coming in. This is surprisingly true almost all the time.
Very large companies will tend to have a mashup of all kinds of technology that is never fully untangled. A very large Corp with little tech debt is exceptionally rare. If it ain’t broke don’t fix it is the rule.
Mid sized corps and late stage startups seem to be the sweet spot. Fairly low tech debt systems that is providing high value is still possible. This is where you have enough maturity to know what “good” looks like, and enough developers, momentum and budget to implement the vision.
They were great places for young adults to complete the transition to “adult”, to experiment and figure how who they want to be.
These days the costs seem to far outstrip the benefits, and the Internet makes so much more accessible at a young age.
Parents and kids are finding it hard to justify hundreds of thousands of dollars just to “figure things out”, as we used to.
It is absolutely not true for most people. Most people need a human guide to show them the way. I am living this now with my two kids, both of whom need instruction (and also help from mom and dad).
I am honestly surprised there is no “2x match for the next 24 hours” or something similar (which again is completely unverifiable).
Really? How would this be enforceable or even discoverable?
I really don’t understand why these firms didn’t use at least two banks for their deposits. Surely these tech firms have heard of single points of failure being problematic?
The flip side of the coin is how do rich people select accountants and wealth managers that they can trust? I have heard so many horror shows of celebrities getting ripped off by their accountants. It seems to happen even more to poor people who suddenly become rich - lottery winners seem unable to hang onto the cash. And the Murdaugh murder trial revealed networks of lawyers and fiduciaries playing fast and lose with client money (one example was a trust manager loaning Murdaugh huge amounts of cash from a trust for two minors who mom was killed in an accident, and the girls got a multi million judgement).
Are there trust networks? Or word of mouth and luck?
How significant is exposure outside of startups and tech companies?
For me it’s because that is slow, tedious and exhausting. Often you need to cover a lot of code surface area to find a bug.
Worse, the bug may be something reported in production in a giant pile of code.
A good set of logs will go a very long way to at least narrowing down where the bad behavior is coming from, and is generally scalabale.
The debugger is useful, but generally only at the extremes of “new to the code, totally clueless” and “really advanced bug that I need to bring out the big guns for”.
The logging approach clicks in really fast the minute you’re talking about a multiprocess program, being microservices or just plain old SOA.
A huge strength of NocoDB is that it is run as just another service accessible your DB that you own.
I can see Virtual Columns being interesting for reporting-type purposes. The mentioned use case of “notations” on data owned by someone else is also interesting. But again - do I really want someone else hosting my data? I don’t know.
Is the target here then basically shadow IT adding onto other people’s data sources that they can’t get the devs to change directly?
In more modern DBs being distributed horizontally, this approach may see a rebound. The big “but” is still costs, in my experience in AWS as an example, managed Postgres Aurora was surprisingly expensive in terms of monthly cost.