Readit News logoReadit News
kotrunga commented on Apple’s Mistake (2009)   paulgraham.com/apple.html... · Posted by u/keleftheriou
singularity2001 · 4 years ago

    >>> Programmers don't use launch-fast-and-iterate out of laziness. They use it because it yields the best results. By obstructing that process, Apple is making them do bad work, and programmers hate that as much as Apple would.
Other than the despotic caprice that one occasionally encounters, this is indeed the biggest reason why I hate Apple's App Store so much.

kotrunga · 4 years ago
I'm a developer, but just to play devil's advocate... think about the end user. Having a review process (though, Apple can improve theirs, see below) helps protect the end user. Programmers, companies, etc. can't just repeatedly push updates non-stop, starting with half-baked apps, iterating too quickly. How do you have a check process that ensures an app is up to standard and "safe"? In addition, the time cost to release adds value to a release, hopefully helping it be more thought out, bringing more value to the user.

Again though... I think the point is that Apple could have a better review process that A) values the developer more and B) shouldn't take as long. I agree with that.

kotrunga commented on Show HN: Login with HN (Unofficially)   loginwithhn.com... · Posted by u/hardwaresofton
kotrunga · 4 years ago
"I'm a yak shaver by trade"

Nice.

Do you have any sites that support the flow yet?

kotrunga commented on Finishing my first game while working full-time   jasont.co/finishing-games... · Posted by u/ntide
levmiseri · 4 years ago
There is one last major piece to be done for the game (now I’m no longer working alone on it) after which I want to write something a bit more detailed about the journey.

But on the high-level — my full-time job is interaction design. Throughout my career I used JavaScript a lot for building interactive design prototypes and it’s the only language I know, so when I had the idea for Yare.io (heavily inspired by MIT’s Battle Code), vanilla JavaScript (and Node for server) was the only thing I could use (didn’t know any libraries or frameworks)

The project was really just a “problem” to be solved. Use JavaScript to move basic geometric shapes on a canvas in a 1 versus 1 battle. It needed to have a UI, rendering of a game state, authentication, event queue, basic ruleset, … None of this really required any tracker or rigorous process. I know what needs to be done, because I’m literally sitting in front it, seeing what needs to be done. It didn’t need a “plan”, because it didn’t matter when each piece of the puzzle was made. Just, whatever I was in the mood for that day.

I think the principle of simplicity (as cliche as it sounds) – trying to keep everything (especially the foundations) as basic as possible – was really the main thing that allowed me to finish the game.

I don't think I could enjoy it as much as I did with some scrum method, brainstorming bullshit, or anything reminding me of work.

kotrunga · 4 years ago
Thanks for sharing!
kotrunga commented on Finishing my first game while working full-time   jasont.co/finishing-games... · Posted by u/ntide
levmiseri · 4 years ago
I have done something similar - building a game while working full-time. But my approach was the complete opposite of this article.

No real process, no plan, no scrum method, not even a trello board to track progress and todos. Personally, I enjoyed the "fun" of it being very spontaneous, yet still passionate. I didn't write to-dos and tasks to be done, because there is always something to be done. And intuitively you feel what's important and what's not. I also didn't want it to "feel" like work.

For context - the game took me about 6 months to create: https://yare.io

kotrunga · 4 years ago
Your game looks like a lot of fun, and the concept is really cool. Would you mind telling us more about your process and the technical aspects?
kotrunga commented on Are daily standups hurting your team?   ideas.krishnan.ca/are-dai... · Posted by u/ajaynomics
hnrodey · 4 years ago
>Shitty standups are first the fault of the leader,

There are no bad teams; only bad leaders. -Jocko

Took me a long time to buy in to this but it's 100% true. Sucky standups are the direct result of an ineffective leader - whoever that may be.

kotrunga · 4 years ago
Woah- this is my first time seeing a Jocko quote on HN. Nice!

And it makes sense- even if the team is "objectively bad", a good leader will help transform them.

kotrunga commented on Can we trust Microsoft with open source?   dusted.codes/can-we-trust... · Posted by u/ingve
sneak · 4 years ago
It's not just services. The most important parts of VSCode are not free software. WSL is designed to make free software users and developers comfortable on a proprietary OS.

Microsoft is also one of the biggest gaming companies in the world (via the xbox platform) and zero initiative on free software anything over there.

Microsoft doesn't care at all about free software, or software freedoms. It's just a means to an end.

kotrunga · 4 years ago
Why was this downvoted? sneak brings up good points.
kotrunga commented on Native speakers are hard to understand in a lingua franca situation   bbc.com/worklife/article/... · Posted by u/sampo
ajford · 5 years ago
This article blames English specifically for what is ultimately a cultural difference. This goes for a native speaker in any language.

I speak passable Spanish, and have encountered the same "cultural dissonance" when dealing with a native speaker in a room full of non-native speakers. When you grow up embedded in a language and culture, you don't realize when you slip into colloquialisms and culture references that don't translate well.

That whole business deal the article opens with is a joke. It's not the native speaker's fault, nor the word's fault. It was the recipient who picked randomly when faced with an unclear choice. If you're unclear, as for clarification. I worked with an international collaboration of scientists during college and that was one of things you learned quickly. No one has the same frame of reference you do, so make sure you're all on the same page. Hell, simply rephrasing your understanding in a reply before you take action can clear this up in a single message. "So you wanted us to X? Got it!". Then the other party has the opportunity to step in and say, "No, do Y".

kotrunga · 5 years ago
this ^

u/kotrunga

KarmaCake day427August 16, 2017
About
software engineer
View Original