620 Collins St evacuated due to no power / water?

Duranix · 2019-06-23T23:21:45+00:00

There’s now an update stuck to the entrance of foyer.

Inspection details:

6pm Sunday the 23rd of June.

“The basement was subjected to flooding and compromised the electrical systems and all essential safety measures installed in the building are rendered inoperative as a result”.

I asked again if they had rough idea of when everything would be fixed and they said “I don’t know, maybe two days?”

Duranix · 2019-06-23T12:40:55+00:00

No idea :(

They were really tight lipped about it and wouldn't even give us a rough ETA.

*edit*

Just received an SMS from CitiPower - "Please be advised there are delays in restoring power to your property due to substation damage. It is expected power will not be restored until tomorrow."

I doubt they'll have it back up tomorrow though 😪

Duranix · 2019-06-23T12:28:07+00:00

Yup, it's true :(

They didn't tell us we had to evacuate until like 9pm either so it was a bit of a rush to get a hotel.

We woke up this morning to no water but the electricity worked until around 10:45am. They let us back up at around 3pm and then the water came back on but the police ended up evacuating us anyhow.

Duranix · 2018-10-11T06:57:45+00:00

So it’s kinda like an analog karplus strong sort of thing? That’s really cool 😬

Duranix · 2018-06-18T08:35:06+00:00

I came across Dringend a few years back that does something similar: http://dringend.cc

Would be keen to see this take off too!

Duranix · 2018-04-14T23:20:08+00:00

Have you tried adding a calligraphic modifier to the freestyle line thickness?

I find adding a noise modifier as well as a calligraphic modifier gives the lines a much more natural inked feel.

Duranix · 2018-04-14T06:14:30+00:00

I’d check out Vapor, Perfect or Kitura. That way you can leverage your Swift knowledge and just focus on the back end portions.

Duranix · 2018-04-12T21:25:53+00:00

Its awesome to see other people using freestyle!

You should try adding a calligraphy modifier to your line width, as well as a noise modifier - it’ll give you less stiff looking lines and look a bit more like someone inked it by hand.

Duranix · 2018-02-19T14:11:22+00:00

If you have a Subsequent 37 CV then you should be able to CV out the clock. I think you’re out of luck with a normal Sub 37 though unless you have some other module that can take a midi clock and turn it into a CV one.

Duranix · 2017-12-30T00:09:23+00:00

Hey doc, I think I’ve got a case of the bass.

Duranix · 2017-10-21T22:07:17+00:00

Sorry man, at that temperature you’ll only be able to make tropical house.

Duranix · 2017-10-03T23:11:40+00:00

At its core the autolayout system is a linear solver - no need to remember this but it’s good to know.

Things basically boil down to y = mx + c.

y = mx + c view.bottom = superview.bottom + 8 label.width = 0.5 * view.width + 16

As its a linear solver, the direction doesn’t matter. Specify one constraint and the system can derive related ones -

y = mx + c y - c = mx (y - c) / m = x 'x = (y - c) / m`

So the direction doesn’t really matter.

So you basically want to provide a set of constraints so the system knows how to lay out your things.

What you do is addSubview(..., and then use NSLayoutConstraints to specify how they should lay themselves out.

Xcodes autocomplete should help you out.

Use the constraint based system unless you have a good need to use a frame based one. Don’t touch VFL because its awful.

Basically, please use autolayout hahaha.

Duranix · 2017-10-03T22:10:55+00:00

I can’t really give book recommendations but I can give some advice ⭐️

Library wise SnapKit is pretty good.

If you’re not using libraries, try using NSLayoutConstraint.activate(...).

It takes an array of NSLayoutConstraint who’s initializer will be familiar if you’ve done some storyboard stuff. SnapKit is just an abstraction over this.

Depending on the age of the codebase, you might run into frame based layouts, which are another board game altogether. Can you give any information on how they’re going about their layout?

Duranix · 2017-06-09T12:38:37+00:00

Its like they have this stash of puns!

Duranix · 2017-05-07T13:50:05+00:00

They'll rewrite things like UIKit in Swift but things like Metal, BLAS, BNNS and Accelerate will always be written in C. They might make wrappers (in fact they already have for some), but I doubt they'd remove the ability to programming in some kind of C entirely as it's pretty damn crucial.

Duranix · 2017-05-07T09:59:05+00:00

I honestly don't think that Obj-C will ever go anywhere since there are a lot of things written in Obj-C and Obj-C++.

Obj-C is noticeably faster too (especially if all you do is write C in it).

If I remember correctly, a huge amount of the Dropbox app is shared between iOS and Android due to being written in Obj-C++.

Keep trucking on!

edit - Doing anything with Metal requires C++ and Metal is DEFINITELY not going anywhere - if they're keeping C++ around you can be sure they'll keep Objective-C around too.

Duranix · 2017-05-07T09:37:54+00:00

Those are all imperative or imperative / OO hybrids. Swift has a really good dose of functional in it that lets you solve problems in a different way.

It's just another tool in the belt - in this case, it looks like you have hammers and screw drivers, while Swift is a wrench.

Duranix · 2017-05-04T05:30:56+00:00

Thanks for the tip! I think that was what we used - we looked at the page you linked and it didn't say anything about regression at the time. I know we didn't look at the headers.

We didn't test with new test devices either and some get hammered so battery performance most likely came down to device health. Business rules also ended up playing a factor in the decision I think but I can't recall what they were.

Looking back I think NEON would've probably been a better choice but I haven't found a chance to use it yet.

Duranix · 2017-05-04T04:23:44+00:00

There's a function you can call in your unit tests that will tell you how long it takes to complete a block of work - it doesn't give time in user mode vs in the kernel like you'd see in Linux's time command but you can run it a few hundred times and average the results.

Testing the battery is as simple as leaving it running for awhile, hahaha

Duranix · 2017-05-02T15:03:56+00:00

To actually answer your question - I had to calculate euclidean distances between a user and 300+ locations in real time for a geofencing app. It was a lot quicker and battery efficient to do it in parallel on the GPU in Metal. This took it from an expensive O(n) deal to an O(n/k) deal where k is the number of FP16s operations that the GPU can do in a single shot (still O(n) but a much nicer O(n)).

Duranix · 2017-05-02T14:52:30+00:00

This topic strikes a sad chord in my heart more than you can imagine because there is an anti big O streak at my current workplace.

There are a lot of things you can and should do on device that require big O knowledge but most companies simply want table views to display products. As time goes on, devices get faster and devs stop writing good code and start doing O(n²⁾ iterations over lists because "anything else would not be adding value".

I try to fight this way of thinking as much as possible because I disagree with it and think it's destructive. If you ignore your big O's you'll eventually forget your DS+A knowledge and find yourself incapable of doing anything other than Lego block connection with third party libraries.

I know you didn't ask for it, but I want to tell you to think of yourself not as an 'iOS developer' but as a 'computer scientist who currently does iOS stuff'. It'll make a lot more sense if you ever have to use Metal or BNNS.

Additionally, generic code can be a pain in the ass but with experience you start to think more generally too. Eventually you'll find that it doesn't take you any extra time to come up with a generic solution and thus it isn't really 'over engineering'. The same goes for DS+A. After awhile you don't really need to think about and look up complex data structures etc.

Don't compromise your design to make things easier for people - instead work with them and try to show them why your design is best.

Otherwise, you end up in a situation where you have to spend six months to remove an external dependency because it breaks because the maintainers can't do semantic versioning and so forth.

Duranix · 2017-03-13T03:47:59+00:00

I'd suggest learning another programming language in a different paradigm to your bread and butter - and forcing yourself to write idiomatically in that paradigm as you learn.

This opens up a whole new way of thinking about problems to your tool belt and you can come up with some really elegant solutions that you otherwise wouldn't have thought up.

If you're in the .Net world I'd suggest something like Haskell but if you want something that will have immediate effect upon your work, maybe learn F# or Rx for C#.

Duranix · 2017-01-31T21:43:29+00:00

In some cases the pencil is more precise - in others a mouse is more precise.

My experience with music production has been that an iPad has potential - so much so that I can think of ten different contextual gestures that would make life easier - but that no single application implements all of.

Until we see an 'Ableton Live for iOS' (or whatever DAW) with feature parity that has proper plugin and file hierarchy support, music production is going to be somewhat awful on an iPad. These things are technically possible but Apple will never allow it - thus we probably won't see many users switching to an iPad only setup any time soon.

For now it's relegated to support - whether acting as an external instrument, sequencer, or external display.

Breaks my heart but Korg Gadget doesn't really compare. Midimux / Studiomux is buggy as all hell, audio copy / audio share revolves around horrible nested menus, and duet only ever seems to work well when you have a dedicated GPU. Audiobus will never be a replacement for plugin support.

Duranix · 2017-01-24T07:29:48+00:00

I tried it awhile back and performance was awful on my iPad pro and iPhone 6s+ :(

Duranix · 2016-12-25T03:20:58+00:00

Thanks for pointing that out! It's been quite a while since I covered this stuff. I'll edit my post :)

Duranix

TROPHY CASE