Forgot your password?

Comment: Re:Spot on (Score 1) 150

by sumdumass (#47950105) Attached to: Dealership Commentator: Tesla's Going To Win In Every State

There is more to it than that. Buying and selling car between commercial entities is highly regulated. For instance, you need a special license to open a new or used car lot, even if that lot is your driveway. Many states even have laws that consider you to be a commercial sales entity if you purchase and sell more then so many cars in a year (5 or 6 in my state).

But you also need special licenses if you want to purchase junk cars, salvaged vehicles and so on. The regulations by the state goes well beyond dealerships getting burned by the manufacturers. Its because the public was harmed- salesman lies about condition of car or the car is a lemon- warranties voided for not being serviced at a specific location or using a specific branded product- selling car with leans on the titles so the new owner ends up getting them repossessed by third parties. There are lots of reasons, even the little old lady who only drove it to church on Sunday stems reasons.

Comment: Re:Spot on (Score 1) 150

by sumdumass (#47950043) Attached to: Dealership Commentator: Tesla's Going To Win In Every State

The law should not bind Tesla or any other new manufacturer to a business model GM and Ford designed many decades ago that puts the new entrant at a competitive disadvantage.

It most certainly should bind them. If you don't like the law, get it changed. But any law on the books needs to apply to everyone equally. Every other automobile company has to play by those same rules. think of how much cheaper toyotas would have been if they were mail order back in the day (and they were both cheaper than American cars and got better fuel economy). How about the Yugo, you saw specials of 2 for one for just $9,000.

If you do not like the laws, get them changed. But until then, anyone wanting to join the circus must erect a tent.

Comment: Re:Some Perspective is in Order (Score 2) 238

I forgot to mention. Get a hobby, do shit outside of work and be passionate about it. Be passionate about life, not work! I look back into my early years how "passionate" I was about work (not knowing the difference between career and work.) That wasn't passion, that was energy inefficiency combined with not knowing WTF I was doing (or how to do it better, faster and more economically.)

Comment: Some Perspective is in Order (Score 3, Insightful) 238

Sources - 18 years of experience doing all kind of stuff, Java, C, C++, DevOps, Enterprisey stuff, Embedded, for commercial and defense sectors. 45 years old, married, two little kids and going back to grad school a third time.

Next year will be the start of my 10th year as a software developer. For the last nice years I've worked for a variety of companies, large and small, on projects of varying sizes. During my career, I have noticed that many of the older software developers are burnt out. They would rather do their 9-5, get paid, and go home.

Family does that. Specially kids. I need to be home early to be with them, read to them, help them eat, clean themselves, let them see me (and feel and understand I actually give a shit). When I was single I would work at any hour. Not anymore. That does not mean, however, that my work is strictly 9-5. I wake up at 5AM to get myself ready, log in, do some work, then get ready (and help my wife get my kids ready). Then I log back to work via VPN from 9 to 10, sometimes going to bed till midnight... with just 5 hours to go sleep to start again.

I easily make 55a week just like that. More if I do work on weekends. But 9-5 is the strict window I use to be in the office.

A lot of 9-5'ers are like that, and in addition to all that, we see the same shit repeating itself again and again, from one employer to the next. So what you call "lack of passion" might actually be work-related pragmatism combined with some physical exhaustion and simply the necessary notgiveashitis gene kicking off to save your brain from dying after witnessing the same inane shit rendering itself at work for the millionth time.

The passion is there, is just that we move it out of work and into other things, like family and career (which is distinct from work.)

They have little, if any, passion left, and I constantly wonder how they became this way.

Life. Life will happen and will change your perspective and priorities. YOU. WILL. SEE.

This contradicts my way of thinking; I consider myself to have some level of passion for what I do, and I enjoy going home knowing I made some kind of difference.

But that is the thing. You are projecting. How do you know that other people are not made some kind of difference? They are likely making a difference *somewhere else*.

Also, as we get older we become more efficient with our time. I can do a lot more know with less time than what I could do when I had 10 years of experience (and certainly much more when I started my career.) We burn a lot of hours thinking it is necessary, we do not know how to prioritize or say no to crazy demands. We freak out, and we go into a professional-related frenzy, willing to burn the midnight oil to compensate for a lot of things.

We have a lot of energy when we start. But energy is not necessarily passion. And not all forms of professional passions are constructive. As we get older, family or not, we learn to pick our battles and seek out the lowest hanging fruits, the 20% that make up the 80%. It is then when we begin to be true engineers, not just berserker hackers.

Needless to say, I think I am starting to see the effects of complacency. In my current job,

Unless you are developing the ultimate shit, or have a wonderful work experience with your managers, or are developing your own business, never, ever, be passionate about your job. Be passionate about your career, but not your job. Your job is the conduct by which you make money using your career. Display work ethics, and be willing to go the extra mile when needed. But don't confuse that with passion. That's just work ethics, which we should all display.

I have a development manager who is difficult to deal with on a technical level. He possesses little technical knowledge of basic JavaEE concepts, nor has kept up on any programming in the last 10 years. There is a push from the upper echelon of the business to develop a new, more scalable system, but they don't realize that my manager is the bottleneck. Our team is constantly trying to get him to agree on software industry standards/best practices, but he doesn't get it and often times won't budge.

Life. I told ya.

I'm starting to feel the effects of becoming complacent.

That is not being complacent. That is becoming burned out. That is your mind and body telling you the situation is not conductive to your mental, emotional and professional development.

What is your advice?

GTFO. Get another job that you like. Rinse and repeat as needed. Learn to be effective with your

Comment: Re:I said it was BS (Score 1) 64

by LordLimecat (#47946151) Attached to: Micron Releases 16nm-Process SSDs With Dynamic Flash Programming

I guess you now realize that's wrong. The main purpose of trim is to avoid reading and writing pages that are unused anyway. The SSD doesn't need to reallocate trimmed blocks, because the OS isn't using that data anyway. Less physical reading and writing == more endurance.

Its not wrong.
  1) TRIM simply alerts the drive when a block is ready for erasure; its right there in the article I linked. Its primary purpose is not reallocation or anything else; its just garbage collection for performance reasons.
  2) The endurance thing is ONLY if the firmware being used is using a hack to implement their own garbage collection which could induce write amplification. It does not, in itself, reduce endurance if the SSD isnt doing anything fancy / out-of-spec.
  3) Reads have no impact whatsoever on endurance. Only write / erase cycles do-- hence why they quote 1000 P/E cycles (where P= program and E= erase)

Now that you've agreed with what I said (trim affects endurance, but in an application dependent way), are you ready to admit YOU had forgotten exactly what the tech does?

From the wikipedia article's opening paragraph:
A Trim command (commonly typeset as TRIM) allows an operating system to inform a solid-state drive (SSD) which blocks of data are no longer considered in use and can be wiped internally.

From Anandtech ....We run into these problems primarily because the drive doesn’t know when a file is deleted, only when one is overwritten. Thus we lose performance when we go to write a new file at the expense of maintaining lightning quick deletion speeds. .....There’s a command you may have heard of called TRIM. The command would require proper OS and drive support, but with it you could effectively let the OS tell the SSD to wipe invalid pages before they are overwritten.

The purpose of TRIM is performance-- NOT ENDURANCE. It has NOTHING TO DO WITH ENDURANCE except insofar as it replaces a manufacturer's proprietary and amplification-causing garbage collection. Older drives dont HAVE garbage collection, and TRIM does NOTHING for their endurance; all it does is eliminate the eventual performance crash.

You REALLY need to read up on TRIM, as you seem to not understand what it is that it does. To repeat: It does not have any effect on reallocations. It does scheduled erasures. If an erasure would cause a reallocation, that would happen regardless of whether it was during a scheduled TRIM, or during a "on-the-fly erase/write".

Comment: Re:So everything is protected by a 4 digit passcod (Score 1) 496

by LordLimecat (#47946043) Attached to: Apple Will No Longer Unlock Most iPhones, iPads For Police

In disk encryption schemes, there is generally a header at the start of the disk, containing the disk's encryption key. This header is itself encrypted, with your passphrase.

This works because the actual encryption key never needs to change; if you ever need to change your encryption passphrase, the system will use your current passphrase to decrypt the existing AES key, will use your new passphrase to re-encrypt the AES key, and will write it back into the header. If you did not use this scheme and instead used the passphrase, you would have to reencrypt the entire disk whenever it changed.

Cracking the AES key would thus involve
  1) Take an image of the entire disk
  2) Pick a new passphrase to check.
        a) Hash the passphrase
  3) attempt to decrypt the header with the hashed passphrase from 2a
  4) attempt to get valid data from the disk using the results of step 3
  5) Do you have valid data?
        --> Yes: You now have the correct passphrase and Key.
        --> No: You have the wrong key, go to step 2 and continue.

A single iteration of steps 2-5 will depend on the exact algorithms and hashing schemes used. If for example no salt is used to generate the hash in step 2, and you use a single round of hashing / encryption, you could perform thousands or millions of attempts per second. I believe on the iPhone they shoot for ~0.2sec per attempt on iPhone hardware, which could mean several thousand attempts on a high-end workstation, and several million attempts on a large cluster.

The only thing cheaper than hardware is talk.