Hey everyone,I'm looking to buy a new e-reader and am looking to crowd source some more recent opinions vs the similar threads from 2024 or earlier.The two biggest new questions seem to be: - Color vs B&W - Writing input vs NoneThe existing criteria still remain, these being: - Price - Screen size - Battery life - Backlight - Physical page turn buttons - Ecosystem (manufacturer,...
1) API implementation - Including tests and docs this should be perfectly acceptable to merge and review independently 2) UX implementation - Feature flagged, dummy API responses, easy to merge + review 3) One quick "glue" PR where the feature can be integration tested etc
This prevents awful merge conflicts, multiple rounds of increasingly complex stacked reviews, and a host of other annoyances.
Is there any reason that the stacked PR workflow is better that I'm ignoring or overlooking?
Not for me, but I'm glad it fits other people's workflows. I just hope it doesn't encourage people to try make poorly reasoned changes!
Like many of you, I have spent more time trying out different applications in the todo list/knowledge management space without finding a solution that has stuck. I've tried aggressive calendar scheduling, todo.txt, Vikunja, a paper planner, Logseq, Notion, and likely others along the way! I now have the suspicion that the issue I'm having isn't the tooling, but the process. The solution I've...
Remote: Preferred
Willing to Relocate: No
Technologies: Python (+ Frameworks), AWS, Linux, Docker, ...
Résumé/CV: https://www.linkedin.com/in/conorjflynn/ | https://blog.randombits.host/resume (PDF Preview)
Email: [email protected]
Hey, I'm Conor, a software engineer specializing in the backend, but capable of using whatever technologies required to get a problem solved. I have experience with large multinationals, but much prefer my time working with startups. I was the first hire in my current company, and am now looking for a new opportunity having helped the company find product/market fit, scale the solution, and reach a position of stability. Most of my details can be found on my LinkedIn, including links to my Github, Blog, and other technical works.
I am a software engineer specializing in Python backends, but have demonstrated ability using whatever technology necessary to best solve the problem at hand. I have experience working with large multinationals, and startups, both in person and on a remote-only basis. My current role is fully remote, and involves software architecture/design decisions, PoC prototyping, DevOps, improving developer tooling, and general purpose programming.
The best place to see my professional experience is on LinkedIn, but feel free to reach out to me by any means you prefer so we can discuss opportunities.
Technologies: Python (+ Frameworks), AWS, Docker, Linux, ...
LinkedIn: https://www.linkedin.com/in/conorjflynn/
Résumé: https://blog.randombits.host/resume/ (PDF Preview)
Github: https://github.com/conor-f
Blog: https://blog.randombits.host
Email: [email protected]
@ Mar 03 2024 08:00
# Unit: kg
# Bodyweight: 70
Squat:
40 12r
65 8r 2s
40 12r
Assisted Pull Up:
bw-20 12r
bw-5 6r
bw 2r
Highly recommended!
1) Can you get the actual code output or will this end up calling OpenAI each function call? 2) What latency does it add? What about token usage? 3) Is the functionality deterministic?
- Getting familiar with new APIs
- Bouncing general knowledge questions off it
- Having "discussions" to interact with it in a Socratic style
- Giving some "personality" to automated services by calling it as an API
I don't have much interest in playing with the internals for now, but I generally like keeping my data personal and the services I use self-maintainable as much as reasonably possible! I also feel like I could find the token limits and price limiting with ChatGPT.
I've accepted that LLMs are useful when taken with precautions. A few tools I've used recently have convinced me on this fact. Alongside this, I've heard first-hand anecdotal experience of LLMs providing great benefit, from asking about APIs all the way to practising languages or summarizing texts.I'm now interested enough to try run one myself and see how it suits my personal workflow. So I...
Try to write monthly about technical projects I've managed to complete. I'm beginning to mix it up to include more recently musings on non-technical topics now however!
I'd love your feedback on how this process could be easier for me, some resources on learning the Grafana query languages, and general comments.
Thanks for taking the time to read + engage!
1) Have you considered how this could be made more mobile friendly? Most places I could see myself using a device like this, I wouldn't have access to WiFi. Is there an equivalent of a USB SIM card adapter that would fit here? 2) What sort of battery life can be achieved with this?
Looks great though! Am very likely to order an iteration of this :)
Any feedback, questions, or potential improvements, please let me know in the comments!
Let me know about any improvements I could make and how I can improve my writing as I want to keep writing more blog posts in the future.