I would recommend The Lean Startup by Eric Ries. It’s a classic that introduced the MVP concept to the world.
And for a bit of different approach, Make by Pieter Levels. This also recommends trying a lot of ideas and seeking what sticks, but perhaps with a more straightforward approach.
I've developed a command-line password manager and authentication application in Rust. Here are the key features:
1. Uses KeePass file format for secure credential storage
2. Supports One-Time Passwords (OTP) for two-factor authentication (2FA)
3. Provides a convenient CLI interface for retrieving 2FA codes
The project, named Passlane, offers a streamlined approach to password management directly from the terminal. It's particularly satisfying to generate 2FA codes via command line!
I use the Passlane CLI for accessing and managing my passwords. Passlane stores the data in a keepass file that I have in Dropbox so that I can access it from multiple devices. On my phone I access it with Keepassium.
About using it for storing keys of other shell scripts/commands: What kind of special functionality this would require? Would you like to, for example, use passlane to extract the password of some script and then pipe it to that script? Perhaps adding that kind of functionality would make sense.
Well say I have U&P or API keys for some network service and I have a little shell script that automates it. I can save the auth info in the script or in a ~/.keys/ file or something and the file system permissions are all that's protecting them.
If my script could retrieve a password from my KeePass DB if it's unlocked, or ask me to unlock it, that would be cool.
Yes, makes sense! I would need to change it to output only the password without all the extra info that only makes sense for humans - could work in this script mode when provided with an additional command line option.
Thanks for that article! One line jumped out at me:
"When I learned about async programming, I realized that for my CLI-based project, I didn’t really need async. So, I removed all async code and the Tokio runtime, which significantly simplified the code."
This implies that you used async before learning it. Does async come along for the ride with "standard" constructs in Rust, such that you have to make an active effort to avoid it?
Forgive my ignorance about Rust if this is a dumb question.
No, it's not like Go, you have to opt into async. (There was a time before 1.0 where it was, but that was removed.)
My reading is that, since their technique was to learn something and then immediately apply it to their project, they began making it async before they realized it was better of without it. Seems like a good learning experience to me, I think this approach is good.
Yes, I had some feature in an earlier version that I wanted to add and the example code I was looking at was async and that made me think that I have to go to that route and also include an async runtime (Tokio). Once I was there, I ended up using async versions of some other dependencies as well.
Later on I then realized that in my CLI app I’m not gaining anything from it as there is no need for any parallel prosessing. It was just making my code more complex.
Reading this makes me want switch jobs. I want to again work somewhere where in the morning I wake up and feel excited to work, instead of feeling forced to work on some stuff that does not interest me at all.
Interestingly right around this was posted here, I happened to talk to a colleague of mine from an adjacent team and I found out that he had worked at Sun. And he was raving about his time there and just how much he enjoyed working there (and money was not even mentioned).
I have come across a few places/companies which do great work and employees just LOVE(D) being there. Here are some on my list:
* Bell Labs
* Sun
* Microsoft
* Google
So, this begs the question: Which companies today (Sep 2023) are the Google's of the early 2000s?
FWIW, I went through all previous threads of this interview and there is no such discussion or mention of any company names.
I’m curious about what is stopping you. I know I’m very privileged to be in a position where there is a lot of doors open, but at least in my part of the world, this seems to be pretty much the common thing for programmers.
I personally think it’s what made my adult life possible at all. I have ADHD and I have a very hard time working on things I don’t find interesting to the point where I might not be a functional adult if I couldn’t. So I’m very grateful that I can job hop and work where I want sort of frictionless. I’ve never had a bad experience switching jobs. I’ve been to some interviews where someone better beat me, which sucks, but I’ve also been to several interviews where it was clear that me and them just weren’t the right fit. The latter has never been a bad experience for me, I’ve even made some friends along the way and sometimes I’ve gotten different jobs because the boss I was talking with knew another boss with a better match in their organisation.
To be undiplomatic, most jobs suck - most work for devs is “enterprise” or web development, usually for companies that are either not tech companies or that the tech is not that interesting.
Even in the prestige companies like Amazon or Microsoft most devs don’t work on greenfield projects but on maintaining the cash cows.
I guess it depends on what you like. I’m fortunate in the way that I like doing most programming. I love building things, even if they aren’t exciting or if they are using “un-cool” technologies. Heck, I even enjoy maintenance work as long as the end goal is for it to never need human eyes again.
What I dislike is typically tied to all the bullshit that comes with programming. Because I’m mentally damaged the way I am, I have to expend an enormous amount of energy to pretend to listen in a daily standup meeting when people I don’t work directly with mill about whatever the code I’m not at all involved with does. Which is how SCRUM “works” in basically any Danish organisation because none of them have teams actually working on the same thing to justify using SCRUM. Or if you bill by the hour, so you can’t help another developer chase down that silly mistake that turns out to be ridiculously obvious because then how do you bill that half an hour in JIRA? Those things are what I personally look to avoid.
So yeah, if you’re not that into programming anything, then I guess it’s harder but it’s still possible. The first thing I did at my current job was to work with solar inverters and collect massive amounts of data from our solar plants. Which was certainly a challenge, I haven’t really read a manual the way I needed to read those solar inverter manuals since I did some silly stuff in C with BitMap images during my computer science education. So those jobs are also out there.
I think at the beginning of my career (I'm 40 and got my first job as a dev at 18) I really was, I just wanted to program and didn't really care what. That led me to enterprise dev as that was the most available work. After a while though I really did feel dead inside, working on stuff I didn't really care about felt like wasting my life. These days I'm doing better but I had to start my own company to truly get over it :)
wow, this really resonates with me as I am 18, straight out of highschool and landed my first job at a swift shop for enterprise programming, I really didn't care where I started, I really just want to pogram stuff
Can you share more of your story and maybe give me some advice, I really don't want to end up burnt out
I don't regret my path at all! I learned a lot at these early jobs, and honestly at 18 I wouldn't have gotten anything better (and for good reason).
I started uni at 19 (math & computer science at a local state university, I didn't have to go into debt for it) and that gave me a big boost in my programming ability (i continued working in that first job part-time throughout school). After that I went through several jobs in the next ±decade and made sure to always apply to places where I'd learn something new and level up as a developer.
At that point I knew a lot better what I wanted & didn't want to do. But I don't think I could have learned that without that experience and I don't regret it as it really helped me hone my skills and learn a lot. I also learned that the people you work with often make a bigger difference to the experience than the product you work on.
...and may I ask, how did your hobby roguelike projects factor into your career? (Hi ido! It's been some years!) Were they significant for gaining skills, or are coworkers and existing codebases crucial for learning from? I often feel like I learn more slowly writing code from scratch rather than studying and contributing to someone else's.
To me, this is the biggest challenge that comes with having ADHD as an adult. The quality of my work slips if I can't find some sort of novelty in it.
It doesn't always have to be greenfield, though. It can be complex and layered with legacy problems, it just has to be something I haven't explored before to be engaging. Right now I'm lucky to have a job where I'm assigned tasks from a variety of projects, modes and tools which really helps keep me focused.
Reality is it is a tight tension between affording a job that is interesting (ie small teams, interesting work, low TC) vs patience for minutiae of politicking, dealing with sociopaths, working on bowels of legacy systems at a big co (with satisfying TC). Even at faangs (especially?) You are working 9999->9999.1 type projects. Even getting to an interesting project or team needs so much networking and branding clout. Now if your question is why do I need the TC - well I guess I made some wrong life choices in going for luxuries like getting a family, a home to live in etc :).
Btw I resonate with not having the patience for bs jobs. Thankfully I don't have ADHD (I think) but working on something I dont enjoy is such a struggle that I have to think of it is a checklist of chores i have to get through the day for the reward at the end - working on side projects in the night! Sad I know.
> Reading this makes me want switch jobs. I want to again work somewhere where in the morning I wake up and feel excited to work
Good god. Imagine if your life's ambition is to find a job that makes you excited to work. A slave who wants to be excited about his enslavement. A slave owner's dream.
True dystopia isn't some brutal authoritarian whipping the slave into submission. True dystopia is one that teaches a slave to want to be the best slave he can be.
Pretty sure slaves didn't have the luxury of switching plantations or careers if they didn't like the treatment. I get the comparison of capitalism to slavery and I agree with it to a degree. But making it a literal comparison is ridiculous.
I originally wrote the CLI to learn Rust. It became a functional CLI tool for generating and managing passwords. Once I had the CLI working and usable, I wanted to have the passwords available also on my phone and on my iPad and I ended up creating an online vault with a web UI and an API.
The CLI can now use the online vault API for storing/retrieving the password data. There is also a webapp that you can use to access the passwords using a web browser - I use that on my phone.
The passwords are stored AES 256 encrypted, and only decrypted in the client using your master password. The master password is never sent online.
mfjordvald is saying that the company serving the video can be in one of these "wrong" US states where captions are required. Does not really matter where Flowplayer Ltd is located.
