I think it depends on your company rather than saying "most". If you are in a software company (i.e. you sell the software you write), then your value is the unique IP you create from writing code. In that case, hopefully a larger portion of your day is coding.
edit: When I say coding, I don't mean plumbing code, I mean something that is actually a unique invention.
I have delivered successfully projects using Scrum, but we were fortunate that our Scrum Master was well trained and a senior engineer. Our CTO also let us figure things out, and helped us when we were blocked. He was genuinely concerned with the team having a balanced workload, ensured we deliver user value and our software was of high quality. Story points were not used as performance metrics but a tool to help provide stakeholders with some estimation, but only when our velocity became stable. Overall, our process was light-weight, we spent most of our time coding, and we pushed hard to deliver value to the user. If we fell short, we learned from it, no blame, just learned.
As a parent, I'm hoping this will reduce the at-home workloads and shift more work towards school. What's the real life value of having students go to school and then spend all-nighters trying to do homework and all the expected extra-curricular?
I wish HN had a central thread feature for discussing oft-debated topics like TDD, microservices, and agile. This way, we could contribute to the conversation instead of constantly rehashing the same points through new posts.
Maybe then question then is how does one get every developer to design and build modules as you have prescribed?
(Recognizing different talent levels across the industry / delivery deadlines). Genuinely curious to know a scalable solution for this.
Be curious to know if anyone who has trademark legal knowledge can answer this question. Since the word Impossible is common, as far as I can gather, if it is for a different industry you indeed could use it?
If you are writing code by yourself and your code base is relatively small, then I agree it's hard to see the benefits at first.
If your team and code base grows, one of the first things you'll notice is a lot of time wasted trying to figure out what parameter types a method takes. If you can imagine, a new person onboarding on your code base and having to figure this out constantly and then forgetting, is pretty inefficient.
TypeScript solves that problem since you declare types explicitly in code. The new person will know exactly the parameter types, the IDE can support you more intelligently, and you'll get upfront compile time errors.
The downside is the initial setup and the extra effort of declaring types, so it comes with a cost, but personally I think the benefit outweighs the cost.
I think it's a business problem rather than a technical one, how do I get people to even know my website exists? Google Maps, Facebook pages, Instagram are your immediate choices.
One challenge I had with the opening statistics in the post is that it treats all books being equal in writing quality and market demand. Just because I write a book, doesn't entitle it to be bought.
I don't doubt your technical skills, this comment is just to help you see the side of the employer. They don't have time to onboard someone on AWS, they need someone to be able to speak "AWS" out of the gate and contribute immediately. General knowledge isn't helpful, when you need to be able to fine tune each AWS specific services.
At the end of the day, those that get hired because of their certificate can't actually take up budget resources and not be able to expertly talk about HA architecture and deliver on a technical roadmap. You can't hide behind a certificate. A technical professional actually needs to deliver a solution to a real-world business problem and when you don't it is highly visible. (Slow service, downtime, lost data, breaches)
If certification is indeed useless, and exams are simply basic marketing exams, it will eventually become a red flag in the hiring process.
I disagree. I've worked with two groups of professionals, those that have certification and those that say they "know" AWS or have working knowledge or experience. It's quite painful to work with the latter when you depend on their expertise.
Give the content a try, you'll find at the foundation of it is building highly scalable distributed system, just that the execution of it is via AWS. You can apply the same knowledge to any cloud platform.
If you are building software in a paid capacity then yes it's a small price to pay. But if you aren't getting paid or getting paid somewhat decently (e.g. study, hobby, open-source) then it's a lot.
It's great they have various editions, to address the above, so if those editions are good, then it makes my point moot.
edited: Recognizing different free subscriptions exists
edit: When I say coding, I don't mean plumbing code, I mean something that is actually a unique invention.