These are fun puzzles but terrible interview questions.
1,718 karma · joined February 2, 2011
These are fun puzzles but terrible interview questions.
There are schemes where you can get fixed price SRECs by signing them over to a 3rd-party. The third-party then give you a fixed amount monthly or quarterly or whatever but it's a significant discount on the auction price.
There are also companies that will give you a lump sum for your 10-years of SRECs up front but like all 'need cash now' schemes there is a significant discount.
We live in an age of marvels.
If society is indeed sick then the cure probably isn’t worth it.
This “simpleness” is part of what makes Java not easy. It is not very expressive. Java (outside of memory management) does not give the programmer a lot of help. You have to explain things to it in excruciating detail, being very specific and never leaving anything out or the compiler will complain.
The lack of expressiveness makes some things really hard. Just look at the number of dependency injection frameworks that exist for Java. Or logging frameworks.
At a certain point of project complexity everyone ends up fighting their language. It feels that with Java that point comes early then most others. But cleverly I think it comes after a level of complexity that most people end up hitting in enterprisy CRUD apps and that’s a big part of why Java is so popular.
1) It’s fast. Like almost C/C++ fast. Yes like any language you can write crappy slow code in Java but it is fast by default.
2) While certainly not an easy language it is a simple language. The number of footguns in Java is pretty small.
There’s only a little of magic that languages like Ruby and Python have. Which of course means the programmer has to be more specific and add lots of boilerplate. And if you get it wrong the compiler yells loudly. And there’s none of the memory management ceremony from C/C++ that everyone gets wrong constantly.
GC can lead to hard to explain madness but your basic enterprise CRUD app is never going to see that.
3) The standard library is awesome. Things like Java collections and concurrency just work: no fuss. And when you need to reach into the back of the tool cabinet the defacto STL provided by Apache is incredible. Need something super specialized like an ordered bidi map in a tree? Apache’s got one and I have faith it’s well tested, decently performant and has good documentation
A decade ago Java could be terrible. There were a lot of people pushing giant XML confine. But even then you could always use code and smart folks did. Today the XML stuff is kept for comparability but the world has moved on. Modern frameworks end up looking and acting a lot like Rails.
Coal is a terrible industry that is destroying the world. It can't go away quick enough.
[1] https://www.washingtonpost.com/news/wonk/wp/2017/03/31/8-sur...
[2] https://data.bls.gov/timeseries/LNS12000000
[3] http://money.cnn.com/2018/03/16/news/companies/toys-r-us-emp...
If you want to engineer software you should start by making transistors ands putting them together into AND gates and work your way up. It will likely take you a lifetime to master the skills unless you can find a programmer to train with (and not a JavaScript hacker).
Let’s not “no true Scotsman” these folks or anyone for that matter. Everyone starts not knowing everything. Everyone ends not knowing anything.
These people are making cool watches where none existed before. Therefore they are watchmakers. The aesthetic design is an equally important part of the package: who cares if that’s were they decided to focus their first efforts. I imagine a large number of us so-called software professionals started the same way: changing an HTML tags color, hacking a new sprite into a favorite game or changing the color of our DOS prompt.
The key to running NT4 for Alpha was DEC’s FX!32. It crosscompiled x86 code to AXP. Thanks to Alpha’s better design this made my 233mhz 21066 a lot faster running x86 code the my Pentium MMX 233.
States and cities can do a lot, and in fact can do a lot more then the federal government because they don't have a 10th amendment restricting them.
https://www.volpe.dot.gov/our-work/truck-side-guards-resourc...
1) The new Bitcoin supply is tightly managed and the miners maintain the current deflationary pressure, ensuring a continued rise in Bitcoin's value.
2) The new Bitcoin is tightly managed, but with the aim of some modest amount of inflation akin to what most central banks aim for. In this model, transaction fees dominate mining profits since Bitcoin's value will stabilize or drop.
3) The new Bitcoin goes into hyper-inflation Weimar Republic-style, eventually becoming worthless.
I think it will be number 3. There is too much money to be made by attempting to time the inflationary spiral, and miners essentially acting as Bitcoin's central bank are in a perfect place to take advantage of it.
The towns also deduped street names, so if one town had a Green St, Green Ave and Green Rd, only on kept its name.
Citation needed.