1. 1

    This is awesome. Now just do this for email and I’d be set.

    1. 8

      I think this looks really nice. But I’m wondering why Lobste.rs needs an app. The mobile web version looks great on it’s own. What benefit does the app have over the mobile web version?

      1. 3

        Possibly being able to cache content for offline viewing? I guess opening the pages up before hand has the same effect.

        1. 3

          If a guy/gal can stomach potentially “losing” some time, I always encourage folks to take a risk and build something. Just because someone doesn’t see value does not mean value doesn’t exist.

          1. 2

            And I’m not saying that this has zero value. Just that I don’t see the value to me. I’m sure the value to the developer is great. Enough at least for them to keep working on it.

          2. 1

            I find Alien Blue a far superior experience for browsing reddit over both the web version Reddit and the web version of Lobste.rs; the integration of things like voting and easy access to the comments beside the story itself is hugely useful, among a plethora of other

            1. 1

              Anything is better than using Reddit’s mobile website. Even if you can find the “compact” version, which is well hidden. Reddit’s mobile website is inconstant, not responsive, impossible to read, and difficult to use.

              On the other hand Lobste.rs web is responisve, beautiful to read, and has it’s buttons sized to fit my finger. Reading the story and voting is easy for me. That’s why I don’t see a need for an app.

              1. 2

                Really? I quite like it and it’s easily found at http://i.reddit.com/

                1. 1

                  I didn’t know it was there. I have had to type in {url}.compact before to find it.

                  As far as layout and usability I think it’s “just OK”, but not great. I think it misses out on the sub-reddit style customizations. Which I know could slow down page load, but I think it’s worth it. They lose so much by not having the mobile version share the same custom styles as the desktop version.

          1. 3

            Nice, can’t wait for the iOS version :)

            By the way, the name sounds a lot like “pinche”, a moderate-severity expletive in Mexican Spanish. Not sure if that’s serious enough to merit changing the name.

            Other than that, pretty exciting!

            1. 4

              Thanks! The name actually came from the lobster in The Simpsons

              1. 4

                True story.

                I graduated High School early and decided to travel Mexico at 17. My poor gringo ears heard the word “pinche” and thought that Mexicans really must like to “pinch” people.

                I also got slapped for using the word “excitado” to ask a girl if she was excited about the football match. Unbeknownst to me, and what my english-spanish dictionary failed to mention, was that “excitado” is slang for horny. My friend later told me that with my poor broken spanish, I basically asked her if Football got her wet.

                Ah, what a young, naive, pup I was.

                1. 4

                  In my, obviously biased, experience this post does not actually describe the realities I’ve seen. The problem is generally managers want new spiffy sound things and hire people to do it. This post makes Albert out to be the villain, but he gave Alice what she was asking for. I’ve had multiple meetings where it ends with “I can do this for you, but it’s going to be expensive and fragile” but it doesn’t matter, they want it anyways.

                  Yes, developers are culpable as well. Some sneak in ridiculous features but I think there is plenty of blame to go around.

                  1. 2

                    What if Zip worked for Alice, or if Albert worked for Zola? That seems more interesting to me.

                    1. 1

                      I’ve seen this played out in multiple ways, I’d imagine more ways are possible as well but:

                      • Zip is successful despite his manager.

                      • Zip is ousted for saying no and the owner does not like to hear no. Replaced with someone that will not say no.

                      • Zip is successful despite his manager but replaced with an Albert after completion that makes a mess of everything.

                    2. 2

                      “I can do this for you, but it’s going to be expensive and fragile”

                      Nice! I really like how you worded this. I will use it in the future. Thanks.

                      1. 2

                        I have found, socially, there is generally value in expressing that you are always willing to do what you’re being told but being blunt about consequences. And depending on who you are talking to, you might be able to suggest an alternative.

                    1. 1

                      Nice. Thanks!

                      1. 6

                        I don’t think in this particular case the hiring decision was inappropriate. If you are a manufacturing company and you are getting a higher order volume it absolutely makes sense to take on more staff (or find other ways to increase your production rate). The mistake made here was not training the workers adequately and not having good quality controls. If the boards were being tested as they were going out of the plant, the issue might have been caught before 9000 bad units were sent to the customer.

                        1. 1

                          I agree, the company’s decision to increase its labor force is totally normal. How quickly they do it and how they train their staff during the on-boarding period appears questionable.

                          1. 1

                            Was thinking the same. Mythical Man Month is about software development, not assembly line production.

                          1. 2

                            Reference for those who want it.

                            Ref: https://twitter.com/patio11/status/451262179858083840

                            1. 6

                              Brook’s “The Mythical Man-Month” covers this well, and is still largely relevant even though it was published in 1975.

                              Anecdotally, I have been involved in late software projects, and as expected there were a few proposals such as “can’t we just add some contractors and speed things up”? Thankfully those managing the projects, in general, carefully explained the lead time for training on the codebase, how this would take time away from those currently working on the code, impact due to disruption, etc. Instead we would usually end up trimming a couple features for the first version, and to lower delivery time enough to be palatable.

                              1. 3

                                I strongly recommend “The Mythical Man-Month” as well. After reading that book, I have found it much easier to see tell-tale signs of a software project going awry. That said, I am surprised the manufacturing company did not push out a small batch of boards (say 100), and send back to the company for testing. This adds lead time, but often avoids major financial catastrophe (such as this case). It can also save your customer money, if the drawing wasn’t quite as thorough as they thought!

                                Hardware prototypes can be absolutely crucial to determining if a) the drawing is correct b) it has been interpreted correctly by both parties and c) gives the manufacturer a chance to become comfortable with the build process and confirm the tiny details which are sometimes missing, even in the best drawings.

                                If this was a misbuild AFTER prototyping, the question turns to how - how did company process controls/QA allow a change to a previously approved build? How can the company prevent something like this again in the future?

                                A lot of food for thought here. Thanks!

                                1. 2

                                  She said there is a thorough control process for getting parts for your builds. If one was lazy, you (the tech) could save time by assuming you know what is best and take parts from other assembly lines near by. Potentially thinking “Flux is flux! It is all the same!”

                                  She has been in the industry a surprisingly long time so she has the knowledge to observe the whole rapid growth and hiring phase and correlate that with poor quality. This clicked with me as I recalled projects that were mismanaged and how I was unable to steer the conversation effectively.

                                2. 2

                                  I find that the majority of CS majors have had to read it. The business manager’s I’ve worked with however tend to have not read the book. And when I have lent my copy out, the consumeristic nature of people (at least in the States) has led some to as me why I loaned them such an old technology book. Appearing to think that newer is better? :(

                                  I really appreciate you sharing. Ideally, I am seeking more current and personal experiences to this ongoing issue. If we could quantify different managerial or personality types maybe there is a common dialect or way in which to communicate this concern and actually be heard. Or maybe you attack it on the front end with a basic risk assessment strategy for producing technology products (software, pc boards, etc).

                                  I realize I’m probably dreaming… :-)

                                1. 3

                                  to answer your question directly: the famous quip (from, i think, “the mythical man month” by brooks) is that 9 women can’t make a baby in a month. and the more politic way of explaining that is to buy someone the book.

                                  BUT… only yesterday i was getting stressed because someone above me decided to shift emphasis in our current work, so there was less technical responsibility for me, with some work delegated to someone else.

                                  i had to sit down and think.

                                  i realised that my response is always to look for a technical fix. because i am a smart guy who can solve technical problems (and i don’t have to rely on someone else who might be flaky). so my natural reflex, when challenged, is to look for a technical solution that i can manage.

                                  and i realised this had caused problems in the past. on a previous project i worked round various issues with technical fixes that ended up causing further issues. not because they were wrong, but because the client didn’t understand them. and when they did, they suggested simpler compromises that we had to implement instead.

                                  so i realised that sharing things with more people sometimes makes sense. and that i am biased, favouring keeping things under my control. in short, i am optimising to lower short term risk of failing, at the expense of the long-term success of a (more client-friendly) product.

                                  now, in my enlightened state ;o) when i read your question, i wonder whether you have a similar reflex. it is safer to keep things local. but it’s not always the best idea. maybe the company needs to grow anyway? maybe this is the cost of bringing in new people, but the long-term gain is worth it?

                                  1. 3

                                    Yeah, growth is going to happen. I’m not arguing against it. More like I’m trying to tie long term growth, risk, and incentives together to have people make sustainable decisions . A poor example would be money markets where the incentives and long term risk rarely intersect. Anyone have a good example?

                                  1. 8

                                    I have no advice to give, but are you sure you should be mentioning the brand of car here? I would imagine that kind of information could be damaging to the company, especially a publicly-traded one.

                                    1. 6

                                      This is not a loss for Tesla. Their shareholders should not be concerned. The loss falls onto the manufacturing company building this part. This company was not named.

                                      Thanks for your concern.

                                    1. 5

                                      Personally, my career has been filled with picking up people’s projects and either;

                                      • Making them work as originally intended
                                      • Shipping new features
                                      • Reversing large code bases with no documentation

                                      As such, I tend to error on the side of verbosity when naming things. Because I’ve been burned by poor/no conventions in the past. Which has cost me time and money.

                                      What struck me is that Michael’s examples look a lot like Apple’s Cocoa code examples.


                                      And given this, it continues to prove that there are different schools of thought about how to approach these conventions (obviously).

                                      On a personal note. My wife and I have been to marital counseling several times. We always come away with more tools than when we started. Some conventions that we have agreed to.

                                      • We agree that we won’t name call
                                      • We agree that won’t subvert each other’s authority with our kids
                                      • We agree that we will discuss financial purchases over (N) amount
                                      • etc

                                      Which leads me to my (what I hope) fairly pragmatic philosophy.

                                      • If I am the Lead Engineer I’ll ask what the team wants to do.
                                      • My vote is that descriptive names are required and that the code base will be maintained with that requirement (code reviews, pairing, etc)
                                      • If I get out voted here, I’m ok with that. As long as the concession is that we consistently keep the agreed upon coding style (If some new “Code Ninja” is hired, they do not get to come in and be “Billy Bad-Ass” and change our conventions)

                                      At the end of the day, you are “married” to the programmers on your team. And your code base is your beautiful and loving child. Conventions are simply communications tools for programmers to manage their family and raise that perfect (har, har) child.

                                      As such, you are free to pick what works for you and your team, compromising with your team mates on any disagreements. But consistency is key.

                                      1. 1

                                        Git and VIM are the two common topics that I run into, that, whenever I study up on them, I learn something absolutely new. I can’t tell if that is a good thing or a bad thing… ;-)

                                        1. 4

                                          With a little misdirection on his part, I wonder if this article would have ever been written. There isn’t a lot there to tie Mr. Nakamoto to the project. The money quote that he lets slip is really the anchor of newsweek’s story.

                                          “I am no longer involved in that and I cannot discuss it,” he says, dismissing all further queries with a swat of his left hand. “It’s been turned over to other people. They are in charge of it now. I no longer have any connection.”

                                          edit: redundant link

                                          1. 4

                                            That quote could easily have been the answer to a question about his government contracting work and not bitcoin.

                                            1. 1

                                              Good point.

                                            2. 2

                                              Agreed. I wonder if he’s not pulling a prank.

                                              Also, I wonder how that reporter got the police to go with her.

                                              1. 2

                                                She said that when she went to his house, he called the police, saying she was endangering him. I imagine his life expectancy is pretty short now; how often do you have half a billion dollars stored in a regular house in the suburbs, by somebody who has few friends and no security guards?

                                                1. 2

                                                  Oh, got it.

                                                  This guys needs to cash out some BC and move his family to the Grand Cayman

                                                  1. 1

                                                    I’ve seen this idea elsewhere too, and it’s sometimes given as meaning that Satoshi can just protect himself if he wants to. But there are several things wrong with such an argument:

                                                    (1) He might not still have access to the BTC. Even if he does, Newsweek don’t know that

                                                    (2) He might not even be the BTC Satoshi; it’s not established beyond all doubt

                                                    (3) Moving house, changing your life, is hard at the best of times, and Satoshi is ill—a fact known to Newsweek before publication

                                                    (4) Satoshi appears to have made the commitment not to spend his BTC. Why force him to spend his own money on security that he ought not to have needed?

                                                    (5) As you point out yourself, it’s not only Satoshi’s security at stake here. Does anyone think that the whole Satoshi family should have to change their lives over this?

                                                    1. 1

                                                      Not to mention that a life in the Grand Caymans doesn’t appeal to everyone. Maybe he’s happy with his life there (or at least he was)?

                                                      1. 1

                                                        I didn’t mean to imply that Newsweek’s behavior is somehow defensible. Or that it will be easy for this person to run away to saftety.

                                                        This Satoshi and his family are basically in for deep upheaval. It’s sortof like a popstar becoming super famous, but not quite rich yet. Dealing with it will be extremely difficult for him and his family (hopefully he does have access to the Bitcoins).

                                                        Does anyone think that the whole Satoshi family should have to change their lives over this?

                                                        Rich people do exist in this country (even richer than this guy). And, in general, I don’t think that their families have to live in fear all the time, or live in something like “witness protection”. The police crack down real hard on kidnapping and other types of extortion. Otherwise, everyone would be a criminal.

                                                        1. 1

                                                          When I was in Sligo, Ireland back in 2000, I met this guy on the dole who invited me over to a house party. We were walking around the neighborhood and he pointed out the house of the local millionaire. It was basically the same design as his house, and it was simply on the corner at the end of the same block.

                                              1. 2

                                                I’ve done a fair amount of this. I liked Aaron’s suggestion on patching Ruby for dtrace.


                                                And his patch.