If you are feeling the way that James does, that the magic is gone... I encourage you to try creating things in a new domain.
Try making music, creating videos, making interactive LED art, building robots, or fabricating toys.
The tools we have today suddenly make it far easier and more fun to experiment with a new craft. What was once daunting is now approachable.
Start by using an AI-powered tool—without shame—to make something superficially 'cool'. Yes, we all know you used a 'cheat code' but that's okay! Now you get to dive in and deconstruct what you created. Tear it apart and learn how and why it works. Go as deep as your motivation carries you. Experiment, hack, and modify.
Just as in software, there will be many many layers of abstraction that you can work through and learn about. Many of them are overflowing with magic and sources of inspiration, I promise.
The gears of capitalism will likely continue to aggressively maximize efficiency wherever possible, and this comes with both benefits and very real costs (some of which are described James's post).. but outside the professional sphere, it appears to me that we are entering a new hobbyist / hacker / creative renaissance. If you can find a way to release enough anxiety and let the curious and creative energy back in, opportunities start showing up everywhere.
Cranking out open source tools one day, endurance racing in IMSA LMP2 the next — I love it. Condolences about the DNF, but truly an impressive run nonetheless (especially the first-lap recovery). Kudos to you and your team.
You're not alone in this. It might be a good idea to delete or edit this post; As currently written, it provides instructions and encouragement to make these connections. :)
Splice | Data and Growth Engineering, Product Design | New York, NY, ONSITE and REMOTE (North + South America) | https://splice.com/
Splice is a creative platform of tools and services that helps musicians stay in the creative flow. Our products are used by a community of professional musicians from bedroom producers to Grammy-winning artists to make better music and to reduce complexity and self-doubt.
We're hiring for a range of engineering and leadership roles, particularly in Data, Growth, and Product Design. See Greenhouse for the list of open positions: https://boards.greenhouse.io/splice
Our technology stack is primarily Golang and Javascript (and Angular on the front-end, but we work with a wide array of technologies. Our primary office is in NYC, but we have a distributed team and are open to remote hires. We also have a dedicated, professional-level music studio in our NYC office (open to employees), and many members of our team are accomplished artists who actively make music.
If you have questions, you can reach me at [my username]
@ splice.com. I am a hiring manager for some of the roles, and can connect you with other hiring managers as needed.
The smoothness is a huge improvement, but touch-latency and scrolling physics are still huge problem areas, even in Jelly Bean on Nexus 7 hardware.
In testing, I've enjoyed the Nexus 7 form-factor, but the iPad's responsiveness and scroll behavior are such a relief when I switch back. It was immediately noticeable, even when beta-testing an app on my old iPad 1 today.
Fair enough, and that's why I attempted to tone down the message with my statement of respect. I've followed Cody's work with interest for years.
I do stand by my general point, though. I think it's worth thinking about how we represent ourselves to the general public. The word "Hacker" has an unfortunate negative reputation, and I don't think messages like this help. It really jumped out at me when I opened the article (otherwise I would have kept this nit to myself).
Was it necessary to wear a t-shirt that reads "It's fun to use learning for evil!" in the photo shoot for a Forbes spread? This doesn't help the negative perception of the word "hacker". :-/
All due respect to the work you're doing – I'm a former member of the security industry myself (worked on the IPS engine at TippingPoint).
At CoffeeTable (http://www.coffeetable.com), we’re combining the best parts of commerce, catalog shopping, and tablet devices to create truly inspiring shopping experiences. Whereas the ecommerce giants like Amazon and EBay are all about searching and comparing technical specs, we’re putting the fun back into shopping. Discover products, shop with friends, and get that same special feeling when you walk into a store and they know your name, your size, and exactly what you’d like but didn’t know it.
Referral Bonus: Refer a candidate that we hire, and win a new, top-of-the-line iPad 3! (64GB, Wi-Fi + 4G)
Looking For:
* Senior iOS developers
* Server-side developers (CT is a Rails shop, but love Python/Django devs too)
* Front-end web developers
CoffeeTable is a small team (2 developers) looking to grow in a big way. New hires will have a huge opportunity to make a big impact across the board, from product direction, to design, to architecture.
Well funded ($2.5MM Series A from Strategic Partners in the catalog industry) and located right across from AT&T Park in San Francisco.
It's relatively straightforward to use CFUUIDCreate as a building block for an application-specific UUID, but you're correct in stating that the API itself simply returns a new, pseudorandom UUID.
Such a thing has existed since iOS 2.0 (CFUUIDCreate [1]), and Apple's updated docs on UDID specifically recommend using CFUUIDCreate. The problem is that an application-specific UUID doesn't address all current use cases for UDID. Specifically, ad networks that support Cost-Per Install (CPI) need to use an identifier that crosses the application boundary.
Push notifications use a device token that is separate from the UDID. An app can only get access to the device token if the user enables push notifications for that app.
EDIT: This is in reply to a deleted question about the impact of an inevitable commercial spacecraft failure.
Great question. In my mind, I compare this to the stigmatization of nuclear power. The combination of the public's lack of trust in science, along with the media's ceaseless quest for sensational (and often fear-based) stories has led to an overly-cautious approach to spaceflight (IMO). This has severely impacted our progress in space exploration; 43 years after the moon landing, we have no active human exploration programs outside the ISS. Embarrassing.
I'm all for improving flight safety and avoiding needless loss of life, but I also believe in taking risks to achieve important goals. Space exploration is worth the risk.
For commercial satellite launches, I see relatively little impact. Existing launch vehicles do not have a 100% success track record, and customers will cover the loss with insurance.
The biggest concern is with manned flights. I'm not really qualified to predict the outcome, but I really hope that pragmatism will prevail. As engineers, we do the best we can, but failures are inevitable. We simply do our best to learn from the failure and take those learnings back to the lab on the next iteration.
As a former engineer on the Atlas V launch vehicle program, I'm so excited to see the commercialization of spaceflight come to fruition. The latest projections I've seen have the Dragon and Falcon 9 coming in at 20% of the price of an equivalent Atlas V / Delta IV (EELV) launch. Comparative Non-Recurring Engineering (NRE) costs are even lower than that. (I'd love if any SpaceX employees can comment further on any of this with more detail.)
As I've seen firsthand, the waste in typical defense contractor programs is obscene – it's so great to see someone doing something about it. Hopefully with much lower cost to orbit, we'll see a revitalization of the commercial launch market as well.
Return-to-libc (a.k.a. ret2libc) is usually used to bypass NX-bit / DEP, but NX was disabled for level04 - the solution does not require return-to-libc.
In the meantime, if anyone wants tips/tricks or just to chat about it, feel free to contact me (email in my profile). I captured the flag late last last week.
Try making music, creating videos, making interactive LED art, building robots, or fabricating toys.
The tools we have today suddenly make it far easier and more fun to experiment with a new craft. What was once daunting is now approachable.
Start by using an AI-powered tool—without shame—to make something superficially 'cool'. Yes, we all know you used a 'cheat code' but that's okay! Now you get to dive in and deconstruct what you created. Tear it apart and learn how and why it works. Go as deep as your motivation carries you. Experiment, hack, and modify.
Just as in software, there will be many many layers of abstraction that you can work through and learn about. Many of them are overflowing with magic and sources of inspiration, I promise.
The gears of capitalism will likely continue to aggressively maximize efficiency wherever possible, and this comes with both benefits and very real costs (some of which are described James's post).. but outside the professional sphere, it appears to me that we are entering a new hobbyist / hacker / creative renaissance. If you can find a way to release enough anxiety and let the curious and creative energy back in, opportunities start showing up everywhere.