@unclebobmartin@EclipsedByNone Didn't see the video? There was nothing he did within that encounter that was illegal. The FAFO moment will be when people have had enough and return the treatment in kind. The RIGHT to carry was not enshrined because of street criminals, but for govt that goes to far.
@BrenMOBoyle@sama Totally agree. Further, does this suggest truth is subjective? I don't believe it is. But if you buy the answer we cannot know a shared truth without 1) experiencing it or 2) truth existing outside our experience.
๐งต1/2 MIT's Charles Leiserson covers the progression from source code to compilation, machine code, hardware interpretation, and ultimately, execution.
๐Full MIT Performance Engineering of Software Systems Course ๐
Scrum Master is NOT a job position or a career path. SM is not an entry-level position. You don't take a class to move from stock clerk to SM. (I've seen people want to do that being frustrated that they can't get "SM work.") SM is a role within the team, and it's often a team member who takes on the role. A lot of an SM's work involves helping the team or teammates do their work in a more-agile way, so knowing how to do that work is important. The "improving Scrum" part does not typically fill your entire day
A cert like CSM or PSM can be valuable, depending on who's doing the teaching, but it covers maybe 0.1% of what you need to do the job. If you want to get a job in an Agile company and have no software-development or Agile experience at all, I'd suggest learning to program or test and then getting a job with an Agile company (or nonprofit) based on those skills. A PSM/CSM will give you a heads up on how Agile orgs work and help you hit the ground running. Once you've done that for a few years and experience what it means to be agile, you'll be in a position to start considering the SM role.
๐ ๐ฉ๐ถ๐๐๐ฎ๐น ๐๐๐ถ๐ฑ๐ฒ ๐ข๐ป ๐๐ผ๐ ๐ง๐ผ ๐๐ต๐ผ๐ผ๐๐ฒ ๐ง๐ต๐ฒ ๐ฅ๐ถ๐ด๐ต๐ ๐๐ฎ๐๐ฎ๐ฏ๐ฎ๐๐ฒ
Choosing the right data store can be confusing with so many options around. This diagram shows a selection choice for a datastore based on a use case (๐ฆ๐ค๐ ๐๐ ๐ก๐ผ๐ฆ๐ค๐).
Data can be ๐๐๐ฟ๐๐ฐ๐๐๐ฟ๐ฒ๐ฑ (๐ฆ๐ค๐ ๐๐ฎ๐ฏ๐น๐ฒ ๐๐ฐ๐ต๐ฒ๐บ๐ฎ), ๐๐ฒ๐บ๐ถ-๐๐๐ฟ๐๐ฐ๐๐๐ฟ๐ฒ๐ฑ (๐๐ฆ๐ข๐ก, ๐ซ๐ ๐, ๐ฒ๐๐ฐ.), ๐ฎ๐ป๐ฑ ๐๐ป๐๐๐ฟ๐๐ฐ๐๐๐ฟ๐ฒ๐ฑ (๐๐น๐ผ๐ฏ). In the case of structure, they can be relational or columnar, while in the case of semi-structured, there is a wide range of possibilities, from key-value to graph.
Image: Satish Chandra Gupta.
Back to you, which database have you used for which workload?
#SQL #NoSQL #Data #Database #AWS
Ten Principles for Growth as an Engineer by Dan Heller:
โThese are the most important lessons that I wish I had learned ears earlier than I did; I sure wish someone had sent it to me when I was 22.โ
1. Reason about business value: Reason like a CEO. Understand the value of your work to your company, and take responsibility for reasoning about quality, feature richness, and speed. Your job isn't just to write code; your job is to make good decisions and help your company succeed, and that requires understanding what really matters.
2. Unblock yourself: Learn to never, ever accept being blocked; find a way by persuasion, escalation, or technical creativity. Again, your job isn't just to write the code and wait for everything else to fall into place; your job is to figure out how to create value with your efforts.
3. Take initiative: The most common misconception in software is that there are grown-ups out there who are on top of things. Own your team's and company's mission. Don't wait to be told; think about what needs doing and do it or advocate for it. Managers depend on the creativity and intelligence of their engineers, not figuring it all out themselves.
4. Improve your writing: Crisp technical writing eases collaboration and greatly improves your ability to persuade, inform, and teach. Remember who your audience is and what they know, write clearly and concisely, and almost al-wavs include a tl;dr above the fold
5. Own your project management: Understand the dependency graph for your project, ensure key pieces have owners, write good summaries of plans and status, and proactively inform stakcholders of plans and progress. Practice running meetings! All this enables you to take on much bigger projects and is great preparation for leadership.
@techyonic Great game. One recommendation is to have someone proof read and correct grammar. Examples are the mis-use of "only" or in this image the word "even" sounds out of place.
If you like #python for #ml and #ai check out #mojo programming lang. Claims a 35,000x perf boost over native python and is a superset of py so you can just drop in preexisting code. Oh, and no CUDA required.