Hacker Newsnew | past | comments | ask | show | jobs | submit | alashley's commentslogin

Between learning Android and actually getting it built, I created a social fitness app that never really took off after an initial influx of users:

https://play.google.com/store/apps/details?id=com.andrelashl...

I'm getting a second wind and might re-build it soon, as something that is more similar to tiktok. I may also need to put much more effort into advertising/marketing this time.


Last time I used call, apply and bind was when a co-worker decided to roll his own JS framework.

It was as bad as it sounds.


Great game, I never finished it, but I've always hoped to find something nearly as far-fetched ever since I played it.


Taking a job as a solo "lead" developer at a startup for my first job out of school.

I picked up so many bad habits and it took a while to figure out how to collaborate with others on code. If I had to take that same path again, I would get involved with an open-source project to solidify the fundamentals.


Can you talk about some of the bad habits you picked up (and maybe how you could have avoided them at the time)?


Sure, here are a few off the top of my head:

- My Git commits/changesets were huge. There were so many code changes to so many files that it was very difficult to review. I learned how to write better commit messages and streamline my commits a few years later.

- I ignored best practices for the sake of getting things done. Programming wisdom and best practices seemed like overkill at the time, as I only measured my work by the number of lines of code I wrote. I needed to find the middle ground between quality and productivity.

- I organized projects/files inconsistently. This was because no one else had to work with the repo at the time.

- I was bad at managing expectations of stakeholders and estimating tasks. Because I was inexperienced, I would over-promise and under-deliver at times. As I went along, I realized better ways of communicating what could and couldn't be done within a sprint. Now, I think when someone asks for a feature -- the answer should generally be yes, with whatever caveats/blockers that are foreseen at the time.


Made this mistake too, good lord.


Persona 5 and derivatives has some of the slickest UX I have seen in any interactive media.


Best: It's okay to say you don't know something

Worst: Don't tell employees you pay them so they shouldn't have to use Google.


Heh. I think the joke is that my company pays me 1 dollar a week to do Google searches, and 2000 dollars week to know which of the 100,000 results is worth following.


That is basically a truth.

If you sit in IT people bubble then you might feel ashamed that you have to look up stuff all the time.

But technicians always had books like "mechanics guide" or "lookup tables" and they mostly knew which things to apply and where. Without training and experience you don't even know what to look for.

IT bubble people overestimate non IT people level of understanding, I see how "normal" people still struggle with basic text editing or using browser features that are obvious to me like "open link in a new tab". I am not talking here about my grandmother but even people in their 20's but just those non IT.


For those new to the joke: https://www.snopes.com/fact-check/know-where-man/

The same goes for knowing when to pay attention to Stack Overflow or GitHub and when not to. ;-)

In fact, it would probably be funnier if it were $1 to implement a new feature with an npm package and $1999 for knowing which npm package to use.

That said, usually when I search HN and stick to recent posts/comments within the last year, the advice often proves useful to some degree, as when experts share their direct experiences. For less technical concerns the same can be true of Reddit.


I took my semi truck to one of the company shops recently. There were some electrical problems that were getting progressively worse.

The technician thought, poked, checked, asked a colleague.

Finally he got out his phone, googled, and disconnected the batteries for about ten minutes. Then reconnected the batteries, and all was well.

I guess something needed to be put to death and reincarnated.

He laughed about it and told me how he fixed it. I laughed too and thanks him, but sometimes that's what you do, and you have to know enough to select the likely or possible out from the unlikely and implausible.


I could be wrong, but it doesn't seem like any of that meal in moderation could predispose someone to a stroke?


A lot of his other food isn't mentioned. The weight around his neck shows his exercise has definitely slowed down. Lack of exercise is a factor for stroke. That is a long term trend for him. He's definitely slowed down over the years and likely hasn't adjusted his diet. I'd guess he's consuming more bread/sugar than that regular supper implies. Likely some long term dietary deficiencies as well.

At 72(?), though, he's still doing better than plenty of others. Full of flaws and imperfections like everyone else but he's doing his thing and apparently enjoying it, so good for him.


I think you missed the part where he said he eats nothing else except some fruit and sandwiches for lunch?


Scary, I'd have similar fears about using Firebase/Firestore in a production app.


A social cannabis app (since its legal where I live -- Canada). It seems like the available alternatives on the app store generally aren't fulfilling their user's needs.


Death Stranding (themes of loneliness/isolation/virtual connection), Persona 5 (themes of evil/corruption/abuse), The Last of Us 2 and Coffee Talk.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: