josephmoniz

> And as horrible as PayPal is, cryptocurrencies have even more friction and risk.

This comparison with PayPal is perfect. The way I see it, ACH and wire transfers are to PayPal what cryptocurrencies are to startups and tech that is being built right now. The reasons why cryptos have more friction at this point of time is because the PayPals of crypto are being built and distributed. I see a future where creating a wallet and accepting crypto payment will be faster, easier and cheaper than signing up for Venmo or Square Cash.

Stripe fees are higher than Solana $USDC transaction fees.

You also don’t have to worry about getting your account shut down or funds frozen. I once worked for a YC company, LendUp, and we started off using Stripe for accepting payment but had to stop because the policies of their partner bank at the time disallowed servicing of our types of transactions. We spent a large chunk of time integrating with many different payments processors on and off, it was rough.

In summary, web3 has the potential to be and already is, cheaper, faster, and permissionless.

As a 13 year old programmer learning to code in 2005, transferring money online seemed impossible, this was pre-stripe after all. A 13 year old getting a bank partnership or a payment processor deal seemed a bit out of reach as well. These days though, sending money online via stable coins like $USDC over a fast and cheap block chain like Solana, Polygon, avalanche, etc is not only possible but flat out inevitable.

Good point, the author clearly misses the point that tests themselves are code and thus can have errors in them as well. Code coverage is just a vanity metric if you're tests don't actually test the correct thing.

This reminds me of a talk from StrangeLoop 2012 by Paul Snively and Amanda Laucher "Types vs Tests". Well worth the watch.

https://www.infoq.com/presentations/Types-Tests

>The pendulum is quickly swinging towards dynamic typing. Programmers are leaving the statically typed languages like C++, Java, and C# in favor of the dynamically typed languages like Ruby and Python. And yet, the new languages that are appearing, languages like go and swift appear to be reasserting static typing?

The author makes the claim that the pendulum is swinging back towards dynamic typing but then follows up immediately with the contradictory evidence that the new hip languages showing up are strongly typed.

I'm curious what if any evidence can be presented that this pendulum is swinging in any direction as oppose to just pulling at opposite ends as it has been for quite some time.

Yeah, this appears to be a bit misleading. It sounds as if they're just running the compiled jar as the /sbin/init process. IMO, thats a very lightweight distro but not a unikernel. #NotAnExpert.

I've been approached by a couple people like this for a technical co-founder position. I got scared off when i actually met them and discovered i had more product experience then them and they had no significant connections or marketing experience to bring to the table.

If you use a persistent PHP stack like mongrel2 + photon an opcode cache is just a waste of a php module.

http://www.photon-project.com/

The final method uses a really common programming idiom for optimizing the removal of elements in a std::vector known as "swap and pop". Swap and pop works by taking advantage of the facts that the most efficient element you can remove from an array/vector is the last one by `pop`ing it off and that the preserved order of the given set isn't important.

    // swap and pop in C++11
    int offset = 2; // remove the second element from the vector
    int end = vec.size() - 1;
    
    auto tmp = vec[offset];
    vec[offset] = vec[end];
    vec.pop();
    // `tmp` now contains the value removed from the std::vector

I wish i could agree. However, my experiences in getting jobs as a software engineer have been vastly different. I've never spent longer then a week seeking a job in the software industry. This might be some what biased because i haven't been working in the industry all that long (just 2 years now). I'm a self educated hacker/programmer that has been writing hobbyist code for myself for 8 years and have never attended a day of college in my life. My average salary for the past 2 years i've been programming has been 90k-100k and my first job was a full time employee for a multi-million dollar corporation in Pleasanton CA and now i work for a startup in San Francisco thats in the alexa top 300 sites.

When i set out to get my first job as a software engineer i was currently working as a system administrator for a conference center in Redwood City. It was the first job i landed when i got back from my first tour of duty in Iraq as a light infantryman. I was still young at the time, 20 years old, still not legally able to consume alcohol yet old enough where most of my friends were already halfway through college. Discontent with going back to college to study computer science with a bunch of people younger then me and knowing that my work as a systems administrator is not what i'd need to be doing on my path to achieve happiness in life i set out to apply to companies seeking software engineers on craigslist.

I spent maybe an entire day sending my resume out over email directly to companies seeking software engineers. I remember being somewhat selective, i'd say i had to have sent my resume out to less then 10 companies that entire day. Although i don't precisely recall the amount of responses i got, i did get a decent amount of responses and almost all of them came in the next day (yes this was 2 years ago). This shocked the crap out of me, i had no previous software experience on my resume, my only previous work experiences were as follows: a warehouse clerk, light infantry and systems administrator. Never the less, i was doing phone screens (and killing them btw) and setting up in person interviews. The very first interview i went to lasted 2 hours and was the first time in my life where i was ever asked to write code on a white board (idk, maybe this is an academia thing). It was a group of engineers interviewing me so that also spiked up the intensity a bit. However, when the interview ended and the HR person came in, she extended me an offer right then and there and said that this is something she's never had to do before. So i went back to my systems administrator gig the next day, turned in my two weeks notice and two weeks later i was officially a software engineer.

My second job seeking experience was very different and also very recent. Having put up enough with the offshore teams crappy code and a horde of rushed employment contractors that couldn't code their way through fizz buzz, it was time for me to look for a new job. So instead of doing any direct applies immediately i just put my resume up on dice.com. That same day my phone was getting barraged with voicemails from technical recruiters. This was going on during work too so i had to turn my phone off for the day. When i got home that night i did do one direct apply and that was to Yelp. I responded to one of the technical recruiters and she set me up with some options and some phone interviews. The next day i got a call from the technical recruiter at yelp to do a quick prescreen and to set me up with a more in depth phone screen with an engineer so i did that. At the same time the contacts from the recruiter were all doing the same thing, calling me and setting up phone screenings that is. The current company i work for right now was moving slightly faster then everyone else though. I did both phone screenings with Yelp and where i work and they both sent me programming challenges to complete and send in. I did them but where i work got back to me faster and set up an in person interview first. So i went and it was a 3 hour interview this time. This time i left without a job offer after the interview but the technical recruiter ensured me that things were looking good. He called me back later that day and gave me an offer over the phone. That was that.

NodePHP anyone? heh, afraid that would be a little more then just a SAPI implementation though, we'd have to throw out a good chunk of the standard library and very few if any extensions were coded for asynchronous execution.

An interesting thought though.

This benchmark seems to be either out dated or somewhat falsified. I ran the same benchmark on my system and CI out performed Yii ( https://github.com/JosephMoniz/BlueElephant/blob/master/docs... ) . The main point though is that with or without caching (APC) CakePHP is the slowest by an order of magnitude.

EDIT: yeah, pretty sure the original Yii benchmark is dated as the graph has older versions while the phpmark repo has slighlty newer ones ( http://code.google.com/p/phpmark/source/browse/#svn/trunk )