Learn to compress information when communicating. Imagine teaching a first day class about $TOPIC. Place the same restrictions: unpredictable questions, time, word count, PRESENTATION.
View quoted note β
Seeking to improve writing skills. I hate old technical articles I've made. Here are some notes I am referencing:
- Wipe out the added frills... No "really", "a bit", "very" etc.
- Remove words that have no purpose to the sentence when put alone. e.g. "I hate old technical articles I've made in the past". "In the past" not needed.
- Additionally, examine every word: a large number donβt serve any purpose.
- No over-explaining. If you think they know then don't write it. Avoid assuming the reader is dumb.
- Try not to put certain adverbs like "surprisingly" to a fact. It manipulates the value on a fact before it could be read. Speak facts as they are truth.
- Use more plain and short sentences. Each sentence contains a thought; Or each sentence contains a fact.
- If a sentence is troublesome to get right, get rid of it.
- What does the reader want to know next?
- Write my thoughts, write against it, see a different perspective, then cut it all into a short outline.
- Practice one sentence at a time. Separate up sentences. Judge each sentence on its own, and prove its worth.
A lot of security talk around these parts but not a recommendation of online security lab and training platforms like HackTheBox. Please try them out if you haven't.
After learning you can try out skills on their lab or CTF platforms. Training on these platforms let you understand how to make more secure applications.
A very long time ago I had my kickstart in my work from doing CTFs. You used to need to hack the login form to get on this web site... I sucked at it and I still do, but you learn a lot extremely quickly and understand how things work far better than just reading on social media.
Many people's questions or suspicions about things could be answered if they just did the security research on whatever they were suspicious about themselves... so do your proof of work.
It's much too early to ask us when we'll have support for the new Pixel 10 phones. They're only available for preorder. We need to have access to the devices and factory images before we can start working on this. If the new Pixels still provide proper alternate OS support, we can support them.
It will be significantly more work than usual to support the new Pixel 10 phones since Android 16 removed the Pixel device trees from the Android Open Source Project. However, that was already only part of what we need for device support and we worked around it by expanding our automated tooling.
We'll be able to use our automated tooling to support the new Pixel 10 devices as long as they still provide proper support for installing another OS like #GrapheneOS with all of the security features supported. We have no reason to believe that's not supported anymore at this time. It's just going to be significantly more work.
Pixel 10 also has much more significant hardware changes than the Pixel 6a through Pixel 9a we added easily. We don't know how long it's going to take yet. We can't estimate that until a while after we've started working on it. We can't start working on it until we have the devices and images.
