ISS SSTV decodes – 6/21/21

The ISS is transmitting SSTV on 145.800MHz this week, June 21-26. I left my laptop running during the day and here’s the decodes I captured. Equipment is an Icom 880h with a homebrew copper wire quarterwave groundplane, and I’m running the RX-SSTV software.

12:32 PT – the highest elevation on this pass was only 22 degrees at 12:34 PT:

12:36 PT:

12:41 PT:

Next pass, 14:09 PT – highest elevation 50 degrees at 14:11 PT:

14:12 PT – probably the best ISS SSTV decode I’ve got so far! :

15:48 PT – there were no ISS passes at this time today, so not sure what this one was:

What is the ‘main thing’ in software development?

Software development is about solving problems. It’s about solving problems in an effective way that adds value. It isn’t about programming languages and writing code. Programming languages are tools. We use tools like Cloud compute to run our solutions, and we build solutions with tools like programming languages and frameworks.

It’s all about solving problems.

If you’re getting started in software development as a career and are putting all your effort into learning a programming language, remember that’s just a tool. It’s how you use it to solve problems which is the important part.

Serverless framework deploy for Java AWS Lambdas

The Serverless framework ‘serverless deploy’ deploys whatever .jar you have packaged and ready to go within your source project.

If you make local code changes but don’t re-build your .jar, serverless thinks you don’t have any changes to deploy:

$ serverless deploy
...
Serverless: Packaging service...
Serverless: Service files not changed. Skipping deployment...

If you’re building a maven-based project, ‘mvn clean package’ first, then run your ‘serverless deploy’.

Working with multiple AWS accounts

Using multiple AWS accounts under an Organization umbrella can be useful even at a personal level, for learning AWS features and self-training, it helps keep various projects partitioned. However, working with multiple accounts at a time can get complex, and on more than one occasion I’ve lost track of which account I’m actually working with.

If you’re working with api keypairs and don’t know which account the keypair is for, the following aws cli command is useful:

aws sts get-caller-identity

It shows you the following info:

{
  "UserId" : ... key id ...,
  "Account" : ... account id ...,
  "Arn" : ... the IAM ARN for the current userid