Curious about the mechanics here — when you say the model was ‘trained on our code base’, was that an actual fine-tune of the weights (e.g. LoRA/adapter or full SFT), or more of a retrieval/indexing setup where the model sees code snippets at inference? Always interested in how teams distinguish between the two.
> It doesn’t have to be nice or pretty EVEN if it’s NOT for you.
> There’s a lot of “theatre” in planning, writing endless tickets and refining them for WEEKS before actually starting to write code, in a way that’s actively harmful for building software.
I'd love to have a "high paying job" where I am allowed to start prototyping and modelling the problem and then iteratively keep on improving it into fully functional solution.
I won't deny that the snowballing of improvements and functional completeness manifests as acceleration of "delivery speed" and as a code-producing experience is extremely enjoyable. Depth-first traversal into curiosity driven problem solving is a very pleasurable activity.
However, IME in real world, someone up the chain is going to ask "when will you deliver this". I have ever only once been in a privileged enough a position in a job to say "I am on it and I will finish it when I finish it... and it will be really cool"
Planning and task breakdown, as a developer, is pretty much like my insurance policy. Because when someone up the chain (all the way down to my direct manager) comes asking "How much progress you have made ?" I can say (OR "present the data" as it is called in a certain company ?) "as per the agreed plan, out of the N things, I have done k (< N) things so far. However at this (k+1)th thing I am slowing down or blocked because during planning that-other-thing never got uncovered and we have scope-creep/external-dependency/cattle-in-the-middle-of-the-road issue". At which point a certain type of person will also go all the way to push the blame to another colleague to make themselves appear better hence eligible for promotion.
I would highly encourage everyone to participate in the "planning theatre" and play your "role".
OR, if possible start something of your own and do it the way you always wanted to do it.
I believe most of FAANGs are indeed like that ? (I was in the stack-ranking kind)
So more likely it is a requirement after all ? I say it to be a requirement because definitely not my personality trait or a skill... so something I need to figure out how to do (depending on if there are more of such team members wherever I land next, if it all in a tech job. Even if there is one such bright spark then they start creating the expectation for others. My manager quite clearly let that out not quite literally but not hard to read between the lines)
The difference is that in this case I will walk in knowing very well that I need to budget time/money/energy into marketing.
Was going through some YT videos from someone claiming to have spent several years in a FAANG and they also mentioned that even the job "turns out to be a marketing" effort in no small part.
I did have a mentor in the job who was encouraging me to "demo as frequently as possible" and that made sense.
What tripped (or triggered even) me was the constant "I am so good, this thing I did made me so happy and all of you must agree" behaviour by the minute... and that was somehow being encouraged. I don't get that...
Anyways, people choose to do what they choose to do (me included). I simply wanted to understand how I should react and adapt (if I do end up taking my next job in tech)
Any kind of brag is certainly not my personality. If I do something I simply do it and end up picking up the next thing. Turns out I need to "announce it and be happy about it" as well.
What's the purpose of RAW+jpg though? Seems rather redundant?
Otherwise, it is wise to highlight that "delete after import" is not a good choice in general.
I personally would not let device A to automatically delete files from device B while files are being copied from B to A.
My workflow is quite manual when bringing pictures in from camera to my MacBook.
- I simply take the SD Card from the camera and then use the SD Card reader on MacBook itself to copy the files (RAW + JPEG) into a working directory.
- Move just the JPEGs into Apple Photos library
- The ones which I think I can/should improve using RAW processing, are processed in DxO Photo Lab and exported to JPEG with a *_DXO.JPEG filename
- DXO Processed JPEGs are added to Apple Photos again. This time due to the naming scheme, the DXO processed JPEGs and camera baked JPEGs are next to each other which helps in quickly checking the results.
- Delete the camera baked JPEG once I am happy with DXO's output
Regarding...
What's the purpose of RAW+jpg though? Seems rather redundant?
...as others have pointed out. Shooting RAW+JPEG is like an insurance policy where if the camera was unable to produce a result which I would like to keep, I have the RAW to play with.
I only keep JPEGs in Apple Photos as all of my image library is backed up to iCloud and don't want that duplication.
RAW files get backed up to another SSD. Looking into a better backup for RAW files.
Also, since I switched recently to a camera which uses CFeB cards for best experience (but also has a SD card slot), the onboard SD Card reader on my MacBook will become useless for this once I get an external CFeB reader.
You can setup a Linux dev VM but unfortunately it won’t have access to the GPU. There is Rosetta 2 support though which works brilliantly with amd64 binaries.
The article doesn’t mention the cutoff speed for L3 though. I think in Germany it is limited to 60km/h or 40mi/h.
Also, only certified in Nevada currently (but California to follow soon). And seems like available only in S class or EQS class.
Basically, for now benefits chauffeurs of expensive limo companies ferrying customers along the Las Vegas strip (admittedly an over simplification for the purpose of humour)
Cannabis legalization and everything else: "We need to study the potential effects for 20 years to be absolutely sure it's safe."
Allowing Mercedes let cars drive 130km/h on their own: "Seems about fine, signed."
Not complaining about the lack of bureaucracy in this case but it is crazy how fast they got the initial law change passed and now they've even updated the speed to 130, even though no car is capable of qualifying yet.
There is(was?) a phrase here: „Wenn Volkswagen hustet, geht es Niedersachsen nicht gut.“ meaning If VW is coughing (the whole of) Niedersachsen suffers.
Apparently said by former chancellor Gerhard Schröder.
Just saying, what if this was an option in Uber Pool and one of the Uber Pool riders was to be an “Ad buddy” ? The “Ad buddy” gets to ride free and other riders get a discount.
