Also recommend "Cat Pictures Please", about an AI that wakes up, loves cat photos, and tries to use subtlety to help humans. https://clarkesworldmagazine.com/kritzer_01_15/
761 karma · joined May 27, 2019
LinkedIn: https://www.linkedin.com/in/johnlmitchell/
Also recommend "Cat Pictures Please", about an AI that wakes up, loves cat photos, and tries to use subtlety to help humans. https://clarkesworldmagazine.com/kritzer_01_15/
I'll check out Flowpipe!
This is critical!
In many teams Devs are "lazy", if any errors or weirdness happens in CI they just wave their hands and say "not a feature, not my problem". Even though they know exactly what's in the test code, the deploy code, and can see the issue.
Letting Devs see and run the CI scripts locally gives them _ownership_. They don't have to fix the issues, but they have control and understanding which radically reduces the arguments and pipeline drama :)
One time I told my producer that for each sentence in her email -- mostly questions -- each sentence translated to an HOUR of my time.
This is fine, I'm happy to work to answer her questions.
However, she was horrified :)
It's easy for people to talk or ask questions without considering the consequences!
- user wants to do X but doesn't know how
- they think that Y will work, and asks for help on Y
- others are confused because Y seems strange
with two caveats:
- a HUGE disclaimer at the top saying "DO NOT MERGE: not tested"
- also, you'll probably want to politely ask someone for a review, and be specific about what you're looking for
"Draft PRs" are fine for discussing topics or code or goals with a team mate.
It's all about getting feedback!
I've met multiple interviewers who said if you know the material, you wouldn't bother with a certificate... For them a cert is an anti-signal for competence in getting a job!
That said, I'm now working on completing Terraform cert. I know the material well, but missed a question in an interview. Investing time/energy in fleshing out my knowledge for the cert will be helpful, even if I don't mention _having_ the cert at all.
Even if one service needs to be developed separately, it can still live in the monolith. For dev, it's easier to test. For production, deploy the same monolith but have it only handle a single service, depending on how it's deployed. You get all the benefits of a monolith while a little benefit of separate services.
Microservices are okay, but "kick up" a lot of issues that can be slow/awkward to solve. Testing being the big one. If the business decides it's worth the exponential complexity then that's fine.
DevOps/Software Engineer with 20+ years experience. ~100 applications this year, a good number of interviews, but no offers yet. (2.5 calls this week scheduled)
It seems I either get:
- proto-startups with ~5 people and no concrete revenue stream, or
- 5k-person enterprises who want someone with a very specific skillset
Both are fine, but they're picky... as am I, so I'm doing my own consulting for a bit.
What happened to startups? What happened to the thousands of 50-300 person companies who need tech work done? The other day a headhunter called me... because they were bored! Rather different from last year when they were juggling 4-5 excited companies in front of me.
Given my experience, I'll be giving a "Fast Developer/Startup" class to a number of companies. That'll turn into a day-long workshop that will be very valuable :)
Strategies:
- DON'T TAKE IT PERSONALLY
- find roles on e.g. LinkedIn, but _never_ do "fast apply": go to the company's site and apply directly
- use a "highlight positives/negatives" tool to draw certain words in a web page different colors. By interactively seeing a mass of green (or orange) you can quickly make a YES or NO decision on a role. I adore the Chrome plugin Highlight This -- https://highlightthis.net/
- apply for jobs on a schedule (e.g. Mon-Wed-Fri), don't just struggle for hours at a time, it's soul-sucking.
- do Studying (job-related tech) interspersed with Fun Programming (generative art!) -- have fun!
- take care of your health and family, go outside and take walks
- DON'T TAKE IT PERSONALLY
Practically, it can be LeetCode. I enjoyed studying LC questions and answers, until I realized it was useless. In 20+ years of Software Engineering and DevOps jobs, I've never used any LC techniques. And if I did, I could research them.
Knowing about different techniques, that they're available, is very useful. But the code, not so much.
XML database ? For a critical service used by 300 M people?
Brrrrrr.....
title is "Complete Short Stories", and yes it's 63 hours long!
I love Ballard, so this is a fine investment.
Summary:
- open important page* on iPhone, using Chrome (* cat photo)
- on Chrome on macOS or Chromebook: three-dots > History > iPhone
There are stanzas for each device I use. The links get synced pretty fast but not instantly, sometimes you have to wait 20-30 seconds.
The above is also an easy way to share a page on the Chromebook, with someone in an SMS message or WhatsApp using iOS. Just reverse the above process.
I listened to the podcast version of this Damn Interesting post: https://www.damninteresting.com/devouring-the-heart-of-portu...
I learned Python first. I saw Ruby as a "similar language, faster, more syntax-heavy, popular in Japan".
Python "won" because of Guido's focus on ease of use by non-programmers. A bunch of scientists used it to steer long-running computations in C, by binding the fast C math libraries with a Python frontend. Python was so easy to use that new scientists and interns could get started easily.
I don't know why Ruby has stalled out. Its "test first" culture and of course Ruby on Rails, and Chef, are all excellent.
Recently while refactoring I realized I was breaking nearly everything. Most code didn't have tests -- I'm working on an experiment.
So, I coded 3-4 tests of the "run the main program and if it doesn't crash then it passes" style. These tests are silly, but they catch lots of refactoring bugs! And it only took 30 seconds to write the test.
If later I decide the actual _values_ matter, I can add another test, but this "break glass" test is already giving me benefits. I can refactor bravely and see how much stuff goes up in flames. Very useful!
I do this even with high-level languages like Python.
On mine I list three attributes that make me a great, and unique, worker for the jobs I'm looking for. Go ahead and be grandiose here -- the point is to start a conversation!
https://docs.github.com/en/account-and-profile/setting-up-an...
One day I realized I was falling asleep on the hour-long, 12-mile route home. (Los Angeles traffic is no joke.) I sold my car and now use metro/bus to commute, or do remote work.
ps: I also can't work from home in my PJs, I "dress up" by putting on jeans :-D
I find Developers like to have a specific Goal, then explore the space towards it. An Artist does the opposite: they make random marks and explore the marks that they "like".
Art iteration is also almost free. In fact, the "cost" of physical media (pencils and paper) helps the human brain understand and integrate what it's learning, vs digital is harder for ideas to stick.
Developers could gain by doing the same thing as artists: do random things to gain knowledge, then create a Goal and work towards it.
Recommend checking out Lynda Barry, who's written multiple books helping students unleash their creativity -- exercise https://www.youtube.com/watch?v=gtb2M2SmeuA
Design Workflow:
- spend little time making a couple design decisions -- lots of handwaving and "we'll figure it out"
- bind these decisions, then write a tiny app to see what it looks like. What are the technical consequences? What are the business consequences (including risks)? How does this affect development?
- repeat 2-4x. The goal is to maximize speed of feedback, at the cost of minimal scope and low quality. That's fine.
- iterate more, expanding the scope and quality as needed
- you're done!
Use high-level diagrams to help focus the effort. This dramatically helps discussions with stakeholders and developers.
Source: writing a book on feedback loops
Recently a company said "no thanks", which is nice of them -- they responded. However, they also said "we'd like to talk to you!". Perhaps they have other roles for which I'm a better fit?
our friend ChatGPT summarizes the paper thus:
"In summary, "Out of the Tar Pit" argues for a shift in software design principles, advocating for the reduction of accidental complexity through functional programming and dataflow concepts, proper state management, and the use of formal methods. By focusing on these principles, the authors believe that software systems can be made simpler, more robust, and easier to understand and maintain."
Note Nick has tons of great content. Example: a video on how to use checklists to reduce risk on operations like database migrations: https://www.youtube.com/watch?v=hOp7uog7_Xw
and the corresponding blog post: https://nickjanetakis.com/blog/creating-checklists-for-high-...
In my experience Sqlite is great for everything, with a number of exceptions: https://dev.to/johntellsall/re-more-on-sqlite-vs-mysqlpostgr...
This site converts HN comments into an RSS feed:
Example URL:
http://hnapp.com/?q=author%3Ajohn-tells-all
I subscribe to about a dozen HN people via RSS. Very often they comment on articles I haven't seen yet. Or, people whose ideas I respect have interesting takes on HN articles.
I blog on everything about Dev, DevOps, and Quality.
A number of topics are on dev speed: fast Dev, fast DevOps (e.g. TDD with cloud resources), fast Startup (post-deploy feedback like A/B testing). Some articles are published, many are in the coffee pot, waiting to be poured out :)
Drop by and say hi!