HN user

jbl

150 karma
Posts0
Comments93
View on HN
No posts found.

I think it'd be good to be prepared to show and explain what you actually did, on the ground to build the business and demonstrate that it wasn't just a side project which you threw up and hoped for the best, but something that you leaned into to make work. If asked, talk about what you learned, what you'd do differently, and how you'll carry those things forward into new opportunities.

As others have said, you can't really control what people will think about having tried and failed to build a business, but you can show them that you put in the work, took some valuable lessons and that those experiences make you a valuable candidate.

Odd. I believe my 2018 model year Volvo allows me to start the car, take the key with me, and lock the doors (so long as I take my key fob with me).

Re the odometers, in my 2018 Volvo and my Wife's 2019 XC40. They are all accurate, but for different purposes.

1. The standard "life of the car" odometer is permanently on the left gauge, top reading

2. There is one (two?) manually resettable trip odometers

3. There is an auto-resetting trip odometer - it resets when the car has been off for four hours.

You can configure which of the second two are displayed by going to in-dash "app" menu and selecting what you want in the "Trip" tab. On my car, this configures the lower displays on the left and right gauges.

Update Re: your high beams - It sounds like you have them on auto. There's a spring loaded ring on the left-hand stalk that engages auto vs. manual high beam. Twist it and the light-with-an-A sign on your dash should change to a normal light symbol. You can then use the twist knob with detents to select parking light vs. low beam and whether you want auto-on or manual on. High beams are engaged by pushing the lever (or you can pull to flash).

I've been going back and forth on this for a while as I work on a product that allows users to build applications in a drag and drop visual manner.

What I've seen is that while novices fairly quickly ramp up and get productive generating basic CRUD apps rapidly, they also rapidly hit a wall in two ways:

1. It can be hard or cumbersome to express more complex logic 2. The drag and drop interface often leads people to -assume- what the runtime will do.

Right now, I'm leaning toward feeling that visualization should be a tool to understand the _behavior_ of what one has written, but not necessarily the thing one manipulates to express a program. Ballerina seems to be this, so I'm excited there!

In the days of friction shifting, it used to be common to mix and match components across the entire drivetrain. You could have shifters, derailleurs, chains, freewheels, and hubs all from different manufacturers.

Drivelines are more integrated now, with derailleurs, cog tooth profiles, chains, and shifters designed as a system with minimal thought given to cross compatibility. At best you could use a non-Campy/non-Shimano chain.

Although, even bicycles (at least those designed for racing) are starting to become more and more proprietary. Try mixing and matching Shimano and Campagnolo shifters and derailleurs or using a seatpost from an aerodynamic frame in another one.

iMessage purgatory 12 years ago

When I switched from an iPhone to an Android handset, I found that I not only had to switch off iMessage, I had to switch it off while my SIM card was still in the iPhone. Switching iMessage off after the fact didn't seem to work.

I do sometimes declare e-mail bankruptcy and just archive/move everything to a folder for later reference. To the OPs point, if something is important, people will generally follow-up.

I think this hints at the crux of the problem. I have no problem with others working long hours, and will even put in a stint here and there when I feel it's warranted.

The problem I see is that it slowly becomes the new norm and benchmark, regardless of whether long hours are productive. These new expectations then get encoded in cultures that devalue those who either choose to spend time on other things or who are simply more efficient.

Do we just need to find better measures of output and figure out what fair compensation for average output is?

I'm working on some apps that make it easy to track time on tasks. The end goal is to be able to build out personal workload forecasts.

The whole thing is built around integrations with existing services. Today, Asana and Toggl. Tomorrow, GitHub, Google Calendar, and who knows what else!

Product management could be a great fit for the OP. However, PM means a lot of different things. Even within one company, day-to-day experiences of PMs can vary a lot depending on the nature of their product or product-area. Some PMs have very broad exposure to the company when bringing a product or feature to market. Other PMs are more marketing and sales leading, while still others focus on learning/developing requirements and writing specs.

My advice to the OP is to set titles aside for a moment and focus on what it is they like doing and where they want their career to go, then work from there to find a position that suits. It might be called product management, product marketing, or it might even be called lead architect or CTO.

The one piece of advice I'd give, though, is that for such broad ranging interests, I think one will need to relax and give up a modicum of direct control, particularly for larger more complex projects. What is it they say about product management? All of the responsibility and none of the authority? Or, more prescriptively, lead by influence.

I'm guessing that most people who are taking the sort of violent action mentioned in the article probably don't understand that.

That may be part of the problem. For most people outside of the tech field, all this technology is just a magic black box that is producing outsized wealth. There isn't a sense that people are doing work to produce this stuff.

- Only work on something as long as I'm productive on it - When I stop being productive, it goes to the end of list and I pick up the next thing and repeat

For big tasks where procrastination might be more of a problem, I put something like "work on x for 10 minutes" and make it a repeating todo until the due date. That way I don't pressure myself into getting some big component done. I can make myself feel good about consistent progress.

I also found that diligently tracking my time on tasks has helped. Now I have a better sense, more or less, of how long common tasks take and can better gauge the time commitment before starting. Before I had data, I think I put off a lot of things or let myself get distracted because I thought something would take an hour when in fact it only takes 15 minutes.

I partially agree, but would add that learning to code is valuable in the same way that trigonometry was valuable. It's another way of looking and thinking about the world. The more perspectives we have on problems, the more ways we as individuals have to attack problems.

I've at least found this to be true in my own experience, but I have also sought out opportunities to combine disparate skill sets and knowledgebases. Being able to toggle between thinking like a sociologist and thinking like a programmer has made my work richer by providing me with solutions I might not otherwise have thought of.

The problem is that "I didn't see the cyclist" becomes a catch-all excuse that law-enforcement takes at face value. This leads to an implicit (though not acknowledged or stated) assumption that a driver cannot be at fault in a driver/cyclist ahem interaction.

I commute to work by bike every day, and every day I watch drivers with their heads down texting, fiddling with the radio, spaced out, or just plain aggressive. If one of these people hit me due to their inattention or actions, I'm pretty sure most police officers (and juries) would just assume accident. In a lot of cases, the incident wouldn't even be investigated.

My girlfriend and sister are both going through surgical training in the US. Here's what I gather:

1. 4 year medical school during which one learns about the panoply of human medicine. You come out of med school with an MD.

2. 4-5+ year general surgery residency (depends on program and optional steps one might take such as research years) during which one learns general surgical procedures through observation, assistance, and practice in the operating room under the supervision of experienced attending surgeons. Generally, residents will rotate through different surgical departments in order to gain broad exposure to the various fields and techniques. Residents take a yearly standardized exam called the ABSITE and are also evaluated by the attending surgeons they have worked with. More senior residents are given more responsibility in patient care and will be given more opportunity to assist and perform in the OR.

3. After residency, one can further specialize by taking on a fellowship (2-3 years, but could be more depending on specialty). During fellowship, one focuses even further on a specific field. Fellowship is an additional layer of practical hands-on training.

4. Practice - after fellowship, one would go on the join a surgical group or create a private practice to perform surgery commercially.

Throughout all of this is a series of examinations that are given which, in total, will allow a surgeon to practice unsupervised on patients.

Edit: to point out where the MD is earned and vague mention of licensure