HN user

twbarber

55 karma
Posts4
Comments29
View on HN

Anecdotally, the low time to prototype has had me throwing usable tool projects up on my local network. I wrote a meal planner and review tool for our weekly vegetable share, and local board game / book library that guests can connect to and reference.

It scratches the itch to build and ship with the benefit of a growing library of low scope, high performance, highly customized web tools I can write over a few hours in an evening instead of devoting weekends to it. It feels like switching from hand to power tools

Hey there! I applied for the Back End role a couple weeks back, but haven't heard anything beyond application acceptance. I'm also in VT! Would love to connect to someone else in the VT tech scene if nothing else. Let me know!

Is this tongue in cheek? I appreciate and try to emulate this trait, but worry it comes off as politic-ing.

This resonates with me. I’ve so far chalked it up to envy of their “unearned” confidence that’s rooted in my own self-esteem issues. Recognizing a fellow imposter in the wild.

This makes battery the primary differentiator for me when I evaluated EVs. As a resident of Vermont, where there aren’t a ton of super chargers the the winters were harsh, range is important. Higher rated mileage in fair weather carries over to winter, even with degradation from cold. We opted for a Model Y, and after a year of ownership it’s still offering the best range for a vehicle we’d consider affordable. Would love to see other manufacturers catch up to Tesla in this regard.

We’ve been using it for 4+ Years for a backend web service and a few other libraries at my current company. I had a chance to document our experience back in 2017[1].

I can’t speak to the approaches to concurrency, but from a day-to-day writing code perspective, it still feels miles ahead of Java in terms of cutting down boiler plate and null safety. Additionally, the support for it in IntelliJ gets better release after release. It’s worth _trying_ to move over from Java, because it’s such a cheap experiment. Add the standard lib, and you get complete interoperability out of the box.

The one caveat to our experience: we did find ourselves switching to Java when we were trying to squeeze as much performance out of something as we could. This was I think Kotlin 1.1 or 1.2, and perhaps the byte code generated now is better, but we did experience some performance hits with the syntactic sugar provided around list comprehension. Overall, however, I much rather prefer Kotlin today if my application is greenfield, and I’ve got a say in how it’s built.

[1] https://medium.com/rocket-travel/kotlin-on-the-backend-at-ro...

Burnout 7 years ago

How did you manage to separate it? I've been remote 2 years now, and I'm just now starting to become aware of how big of a problem this is.

People say getting communication on their phones is like an anchor to their desk

I’ve been struggling with this lately, to the point where I’ve experimented with going back to a dumb phone, and trying to use my smart phone without Slack. As a remote employee, I think having Slack on mobile has lead to a greater degree of freedom, as you mentioned, but I also wonder if the constant tether is leading me to burnout more quickly.

Also born and raised in the Saratoga area, and that's where we live now. We moved back here because of family, and my also one of the local colleges has an outdoor education program my wife wanted to enroll in.

Switching from part-time to full-time remote is what allowed us to move here. We found ourselves spending most of our vacation time back this way anyway, so moving back here was a goal a year or two after we moved to Chicago.

If I ever lost this job, the backup plan is Boston while my wife stays with my family and finishes her degree. There's really not many places to work up this way, and none of them are willing to pay large city wages.

That said, we don't intend to settle down here. The risk is too high. Portland, ME is similar culturally with more opportunity. That's on our short list to head out to next.

I've got a wife but no kids, and have been working entirely remote for 9 months. The 3 biggest changes I've noticed:

- I have to remind myself to slow down when talking to people. I think this is a result of having to think/talk through issues on my own during the day. Pairing with team members has helped this a bit.

- I had to make a real effort to see my friends more often, loneliness set in heavily despite having a spouse. Picking up a social hobby, rock climbing in my case, has also helped.

- If living in an area without a strong software community, exchanging ideas and "talking shop" goes away. Learning and professional growth is now done entirely remote as well. Try and stay in an area with regular meetups or some sort of interaction with other engineers if you growing as a technical contributor is important to you.

I do get back to the office 3 times a year, but it's definitely changed my normal social patterns. I still strongly prefer full time remote to having to commute even once or twice a week, but I now use that commute time for socializing and hobbies instead. Good trade off for the added bit of loneliness in my opinion, although I'm not sure my answer would be the same if I didn't have my spouse to keep me company.

* I also moved from Chicago to a town of 15k in Upstate NY