> It appears some states are already legally recognizing smart contracts
That's good to see.
FWIW I don't like the idea of a future where we need special solidity lawyers to verify some code matches its legal obligations. Which is why the Ricardian format is so appealing. It should be accesible to all
The point I'm making is we can agree some paper is truth or that a distributed ledger is truth.
Failing to send a transaction should void the sale in the first place e.g. Hashed time locked contracts. With some proof of authority logic we can facillitate updates to the ledger by courts or governing bodies i.e the same as adding some new paperwork currently
I really appreciate having a high-level diagram of system architecture when joining a new project. It gives me an instant feel for whats going on and even if its slightly out of date it gives context to the evolution and design decisions of the codebase since then. That said, there's nothing that beats the good ol' step debugger and diving into the code first hand. They're complementary. Without the diagram its kind of like building a mental model of a room by feeling it out in the dark.
Edit: I'm not too strict on UML exactness, as long as it gives a feel for the components, data flow, etc.
And when you can't debug... since no person in the company can build the code in Eclipse, or run it locally.. you look at the gigantic logs full of soap xml dumps. At least that's my experience.
All the people who develop OSS in their free time.
Text editors, plugins, kernels, package managers, compilers, the list goes on in any ecosystem.
The number of these projects I interact with knowingly and unknowingly on a daily basis is ridiculous and represents the cumulative effort of many.
My day job is all the better for it, so I take my hat off to those awesome folk.
Thanks for all the hard fought PRs, features, and optimizations that make our lives as developers what they are today.
Most of the time because companies are hiring out of necessity.
They either need to deliver more, faster, or are lacking technical leadership / expertise.
This means the team is under enough pressure to deliver as is and don't have resources or incentive
to onboard a junior.
My advice is to keep learning on your own time, push yourself to learn a valuable skillset e.g. React (as you say you do frontend)
and make something with it.
For a new hire getting familiar with a project is a given, even a senior needs time to do this.
However knowing a language, framework, or skill is your responsibility before applying for a job.
I've applied for jobs that were above my experience level but ended up getting hired anyway
while I didn't have enough "years" under my belt I knew the domain and tech stack required for the job.
This often meant when applying for a senior job I'd get signed as an intermediate and same with intermediate roles where
I was hired as a junior. Once your foot is in the door, if you work hard it will be apparent that you're adding the value
of more experienced member than your current job title and from there its an easy promotion discussion.
Just my 2cents. Know your stuff, that's your job and stay humble the promotions and opportunities will come.
> In my opinion everyone company likes to only benefit from experiences earned elsewhere but never like to provide folks a place to earn the same in their company
There are certainly many moving parts- but there's nothing quite like running kubectl create -f <somefile> and sitting back to watch your entire application stack spin up
The canonical example of serverless is for handling web requests i.e. 1 function per HTTP route. Database will still need to be on a static server. Managing user login / state etc. will be cumbersome across multiple different functions, however the email and payment processing handlers may be better candidates for serverless functions. A thin front-end and DB on static servers with serverless used for emails+payment processing would be a good initial architecture
It can be abit of a pain if you're not using linux OS as the server.
Setting up secure image registries or registries in general is also tricky.
It can be tricky learning how to debug dockerised applications because of the extra layer of indirection.
Click bait of a title... I think the more important thing this article is trying to say is: use a good heuristic to solve your problem, if it can't do so then ML may be something to look into.
That's good to see.
FWIW I don't like the idea of a future where we need special solidity lawyers to verify some code matches its legal obligations. Which is why the Ricardian format is so appealing. It should be accesible to all
Btw thanks, that harvard link is a good read!