cheshireoctopus

Not necessarily tiny, but awesome single-purpose gardening tool for removing weeds without overworking your back.

That said, here are some tactics I've used over ~2 years as a solo founder to try to keep it together:

1. Focus weeks on certain functions - ie work on developing features for one week and then switch to marketing tasks the next. Admittedly harder than it seems, but when actually followed, find I make considerable progress on that week's topic of focus. Also forces me to accomplish harder work (marketing/sales for me) vs. retreating to what is most comfortable (developing).

2. Speaking with other founders / leaders in the space I operate. This has been especially helpful as I've struggled with a growth/marketing strategy and speaking with others selling adjacent products in the same space has unblocked me many times.

3. Keeping realistic expectations that I'm doing this solo and it will be very difficult at times. Also harder than it seems.

4. Keep a founder's log to persist notable events and learnings. Useful when feeling particularly overwhelmed as I can revisit how much has been accomplished.

Purchased a keyboard from them back in 2015/2016 and really enjoyed the few months that it worked. There is something about those springs... When it stopped functioning a short while later I contacted Unicomp asking how I could fix and/or replace it and was told I'd have to buy a new one.

Probably meant to be as I developed the need for an ergonomic keyboard. Purchased a Kinesis Freestyle2 and it's worked without issue.

Given the forum, going to assume you are seeking an internship in tech.

FWIW, I created/lead an internship program for software devs at a small(er) venture-backed startup. The program was responsible for hiring ~20 interns over two years.

Among the interns I hired, those that stood out had a demonstrated genuine passion for the field as well as our company, had deployed their own side projects to production, and were very very clear in what they were seeking to gain from an internship with us.

Also, very early in my career, I recall a discussion with an intern on how he landed the role at the company I was with at the time. He said he cold-emailed the CEO. He also said that was how he had landed an earlier internship at Amazon!

This is the focus of Matt Taibbi's "Hate Inc."

Looks cool, but would like to be able to check out an existing demo lesson before signing up.

If we consider it a speculative investment, then, sure, at this point in time, BTC looks like a solid investment! BTC investments have funded a number of my vacations :D

But, if we consider BTC a form of currency, I would say it is a total failure given its wild fluctuations in value.

Curious what others think? Want to change my mind!

How can I meet people around me who have already setup a collection point, a community point, or a machine shop?

Do you have an onboarding guide for beginners who are looking for low-effort ways to explore what you are doing?

I used https://www.sleepcycle.com/ for a number of years while suffering sleepless nights.

It seemed accurate...but I had no way of verifying the quality of my sleep. I have heard this is difficult to do.

Eventually I got sick of paying the subscription and agonizing over my sleep data.

I spent probably six months practicing sleep hygiene (consistent schedule, limiting screen time, working out, etc) and removing myself from stressful environments. I was eventually was able to return to a decent schedule.

I also found speaking with a psychologist to be helpful here.

Hope your sleep improves.

You can also be a bit cheeky and call them out and then use it for marketing!

https://medium.com/@zreitano/on-behalf-of-hims-patients-than...

Setup coffee/walk with teammates.

Work on internal hack projects.

Purge the backlog.

I am really into what you are building here - are you looking for volunteers to help?

Few questions if you do not mind:

1. How did you broadcast your Meetup to your students?

2. It looks like you have students pull lessons from a repo. Do you find it challenging to manage a handful of students who are all at different places in your lessons?

3. How do you avoid burnout?

4. Do you plan on open sourcing your lessons?

I am under the impression my manager is trying to get the next role.

If I am able to understand, and perhaps even address, my manager's concerns, then I can help them manage themselves onto the next level.

Interesting advice with #3 - have not considered this before. I like how your approach empowers dev A and, as you say, "ends in trust".

2. Lead by example - be the change you wish to see

3. Focus on strengthening your team members (designers and product managers included!)

4. Ensure your engineers are given ownership and leadership opportunities

5. Do not be afraid to let someone else lead - actually encourage this

6. Do not overload yourself (surprisingly easy to do)

7. Expect the amount of time you spend developing to decrease

8. Expect the amount of time you spend in meetings to increase

9. Actually spend time learning the business your code supports

10. Become a resource to the non-technical ppl your team supports

A lot of good advice in this thread, but remember to have patience with both yourself and your team as you take on this new role. Nothing changes overnight and it might be a number of weeks/months until you find your groove.

Congratulations and best of luck.

Interesting. This anecdotally appears to be the case. Is there anything to back this point up?

Interesting.

Curious how many people actually evaluate the morality of their prospective employers.

Related: very happy to see that https://forum.bodybuilding.com/ is still around/thriving.

> The Boy Scouts have a rule: "Always leave the campground cleaner than you found it." If you find a mess on the ground, you clean it up regardless of who might have made the mess. You intentionally improve the environment for the next group of campers. Actually the original form of that rule, written by Robert Stephenson Smyth Baden-Powell, the father of scouting, was "Try and leave this world a little better than you found it."

> What if we followed a similar rule in our code: "Always check a module in cleaner than when you checked it out." No matter who the original author was, what if we always made some effort, no matter how small, to improve the module. What would be the result?

http://programmer.97things.oreilly.com/wiki/index.php/The_Bo...

Apply it as you go. Piece by piece. Perhaps encourage your fellow developers to adopt the practice.

scary.

> The Bay Area isn't for everybody and it isn't certainly for me, so I hope that not every city try to emulate that and try to find their niche.

Good point.

I'd wager a guess that most developers on HN don't even touch the stuff.

a) is a wealth manager b) is not advocating a populist eat-the-rich" revolution c) doesn't use the keywords "1%", "rich", or "banker" as you imply (I fail to see why you want to bring Judaism into this?) d) does not imply "if you're rich you're a parasite and should be stripped of your property's wealth"

Here, for your convenience, is the author's thesis:

"A bloated and out-of-control financial sector does not add any value to society. Society benefits when the financial sector is kept as small as possible."

The author is ranting on the size of financial institutions, not the rich. Hope this clarifies things for you.